Device configuration for time sensitive network bridge

ABSTRACT

A wireless device sends to an access and mobility management function (AMF), a message comprising a time sensitive networking (TSN) bridge capability support parameter that indicates that the wireless device supports a TSN bridge functionality. The wireless device receives, from the AMF and based on the TSN bridge capability support parameter, a configuration update message comprising at least one route configuration rule. The wireless device sends, to the AMF, a request to establish a protocol data unit (PDU) session, the request comprising one or more configuration parameters determined based on the at least one route configuration rule.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/806,185, filed Feb. 15, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per anaspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a networknode in a 5G system as per an aspect of an embodiment of the presentdisclosure.

FIG. 4 is a system diagram of an example network node as per an aspectof an embodiment of the present disclosure.

FIG. 5A and FIG. 5B depict two registration management state models inUE 100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 6A and FIG. 6B depict two connection management state models in UE100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 7 is diagram for classification and marking traffic as per anaspect of an embodiment of the present disclosure.

FIG. 8 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 9 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 10 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 11 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 12 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 13 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 14 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 15 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 16 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 17 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 18 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 19 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 20 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 21 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 22 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 23 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 24 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 25 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 26 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 27 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 28 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 29 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 30 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 31 is an example call flow as per an aspect of an embodiment of thedisclosure.

FIG. 32 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 33 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 34 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 35 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 36 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 37 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 38 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 39 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 40 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 41 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 42 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 43 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 44 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 45 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 46 is an example diagram as per an aspect of an embodiment of thedisclosure.

FIG. 47 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure.

FIG. 48 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EXAMPLES

Example embodiments of the present invention enable implementation ofenhanced features and functionalities in 5G systems. Embodiments of thetechnology disclosed herein may be employed in the technical field of 5Gsystems and network slicing for communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to 5G core network and 5G systems for network slicing incommunication systems. Throughout the present disclosure, UE, wirelessdevice, and mobile device are used interchangeably.

The following acronyms are used throughout the present disclosure:

5G 5th generation mobile networks

5GC 5G Core Network

5GS 5G System

5G-AN 5G Access Network

5QI 5G QoS Indicator

AF Application Function

AMF Access and Mobility Management Function

AN Access Network

CDR Charging Data Record

CCNF Common Control Network Functions

CIoT Cellular IoT

CN Core Network

CP Control Plane

DDN Downlink Data Notification

DL Downlink

DN Data Network

DNN Data Network Name

F-TEID Fully Qualified TEID

GPSI Generic Public Subscription Identifier

GTP GPRS Tunneling Protocol

GUTI Globally Unique Temporary Identifier

IMSI International Mobile Subscriber Identity

LADN Local Area Data Network

LI Lawful Intercept

MEI Mobile Equipment Identifier

MICO Mobile Initiated Connection Only

MME Mobility Management Entity

MO Mobile Originated

MSISDN Mobile Subscriber ISDN

MT Mobile Terminating

N3IWF Non-3GPP InterWorking Function

NAI Network Access Identifier

NAS Non- Access Stratum

NB-IoT Narrow Band IoT

NEF Network Exposure Function

NF Network Function

NGAP Next Generation Application Protocol

NR New Radio

NRF Network Repository Function

NSI Network Slice Instance

NSSAI Network Slice Selection Assistance Information

NSSF Network Slice Selection Function

OCS Online Charging System

OFCS Offline Charging System

PCF Policy Control Function

PDU Packet/Protocol Data Unit

PEI Permanent Equipment Identifier

PLMN Public Land Mobile Network

RAN Radio Access Network

QFI QoS Flow Identity

RM Registration Management

S1-AP S1 Application Protocol

SBA Service Based Architecture

SEA Security Anchor Function

SCM Security Context Management

SMF Session Management Function

SMSF SMS Function

S-NSSAI Single Network Slice Selection Assistance information

SUCI Served User Correlation ID

SUPI Subscriber Permanent Identifier

TEID Tunnel Endpoint Identifier

TSN Time Sensitive Networking

UE User Equipment

UL Uplink

UL CL Uplink Classifier

UPF User Plane Function

Example FIG. 1 and FIG. 2 depict a 5G system comprising of accessnetworks and 5G core network. An example 5G access network may comprisean access network connecting to a 5G core network. An access network maycomprise an NG-RAN 105 and/or non-3GPP AN 165. An example 5G corenetwork may connect to one or more 5G access networks 5G-AN and/orNG-RANs. 5G core network may comprise functional elements or networkfunctions as in example FIG. 1 and example FIG. 2 where interfaces maybe employed for communication among the functional elements and/ornetwork elements.

In an example, a network function may be a processing function in anetwork, which may have a functional behavior and/or interfaces. Anetwork function may be implemented either as a network element on adedicated hardware, and/or a network node as depicted in FIG. 3 and FIG.4, or as a software instance running on a dedicated hardware and/orshared hardware, or as a virtualized function instantiated on anappropriate platform.

In an example, access and mobility management function, AMF 155, mayinclude the following functionalities (some of the AMF 155functionalities may be supported in a single instance of an AMF 155):termination of RAN 105 CP interface (N2), termination of NAS (N1), NASciphering and integrity protection, registration management, connectionmanagement, reachability management, mobility management, lawfulintercept (for AMF 155 events and interface to LI system), providetransport for session management, SM messages between UE 100 and SMF160, transparent proxy for routing SM messages, access authentication,access authorization, provide transport for SMS messages between UE 100and SMSF, security anchor function, SEA, interaction with the AUSF 150and the UE 100, receiving the intermediate key established as a resultof the UE 100 authentication process, security context management, SCM,that receives a key from the SEA that it uses to derive access networkspecific keys, and/or the like.

In an example, the AMF 155 may support non-3GPP access networks throughN2 interface with N3IWF 170, NAS signaling with a UE 100 over N3IWF 170,authentication of UEs connected over N3IWF 170, management of mobility,authentication, and separate security context state(s) of a UE 100connected via non-3GPP access 165 or connected via 3GPP access 105 andnon-3GPP access 165 simultaneously, support of a coordinated RM contextvalid over 3GPP access 105 and non 3GPP access 165, support of CMmanagement contexts for the UE 100 for connectivity over non-3GPPaccess, and/or the like.

In an example, an AMF 155 region may comprise one or multiple AMF 155sets. The AMF 155 set may comprise some AMF 155 that serve a given areaand/or network slice(s). In an example, multiple AMF 155 sets may be perAMF 155 region and/or network slice(s). Application identifier may be anidentifier that may be mapped to a specific application trafficdetection rule. Configured NSSAI may be an NSSAI that may be provisionedin a UE 100. DN 115 access identifier (DNAI), for a DNN, may be anidentifier of a user plane access to a DN 115. Initial registration maybe related to a UE 100 registration in RM-DEREGISTERED 500, 520 states.N2AP UE 100 association may be a logical per UE 100 association betweena 5G AN node and an AMF 155. N2AP UE-TNLA-binding may be a bindingbetween a N2AP UE 100 association and a specific transport networklayer, TNL association for a given UE 100.

In an example, session management function, SMF 160, may include one ormore of the following functionalities (one or more of the SMF 160functionalities may be supported in a single instance of a SMF 160):session management (e.g. session establishment, modify and release,including tunnel maintain between UPF 110 and AN 105 node), UE 100 IPaddress allocation & management (including optional authorization),selection and control of UP function(s), configuration of trafficsteering at UPF 110 to route traffic to proper destination, terminationof interfaces towards policy control functions, control part of policyenforcement and QoS. lawful intercept (for SM events and interface to LISystem), termination of SM parts of NAS messages, downlink datanotification, initiation of AN specific SM information, sent via AMF 155over N2 to (R)AN 105, determination of SSC mode of a session, roamingfunctionality, handling local enforcement to apply QoS SLAs (VPLMN),charging data collection and charging interface (VPLMN), lawfulintercept (in VPLMN for SM events and interface to LI System), supportfor interaction with external DN 115 for transport of signaling for PDUsession authorization/authentication by external DN 115, and/or thelike.

In an example, a user plane function, UPF 110, may include one or moreof the following functionalities (some of the UPF 110 functionalitiesmay be supported in a single instance of a UPF 110): anchor point forIntra-/Inter-RAT mobility (when applicable), external PDU session pointof interconnect to DN 115, packet routing & forwarding, packetinspection and user plane part of policy rule enforcement, lawfulintercept (UP collection), traffic usage reporting, uplink classifier tosupport routing traffic flows to a data network, branching point tosupport multi-homed PDU session(s), QoS handling for user plane, uplinktraffic verification (SDF to QoS flow mapping), transport level packetmarking in the uplink and downlink, downlink packet buffering, downlinkdata notification triggering, and/or the like.

In an example, the UE 100 IP address management may include allocationand release of the UE 100 IP address and/or renewal of the allocated IPaddress. The UE 100 may set a requested PDU type during a PDU sessionestablishment procedure based on its IP stack capabilities and/orconfiguration. In an example, the SMF 160 may select PDU type of a PDUsession. In an example, if the SMF 160 receives a request with PDU typeset to IP, the SMF 160 may select PDU type IPv4 or IPv6 based on DNNconfiguration and/or operator policies. In an example, the SMF 160 mayprovide a cause value to the UE 100 to indicate whether the other IPversion is supported on the DNN. In an example, if the SMF 160 receivesa request for PDU type IPv4 or IPv6 and the requested IP version issupported by the DNN the SMF 160 may select the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 may support thefollowing mechanisms: during a PDU session establishment procedure, theSMF 160 may send the IP address to the UE 100 via SM NAS signaling. TheIPv4 address allocation and/or IPv4 parameter configuration via DHCPv4may be employed once PDU session may be established. IPv6 prefixallocation may be supported via IPv6 stateless autoconfiguration, ifIPv6 is supported. In an example, 5GC network elements may support IPv6parameter configuration via stateless DHCPv6.

The 5GC may support the allocation of a static IPv4 address and/or astatic IPv6 prefix based on subscription information in a UDM 140 and/orbased on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF 110) may handle the user plane path of PDUsessions. A UPF 110 that provides the interface to a data network maysupport functionality of a PDU session anchor.

In an example, a policy control function, PCF 135, may support unifiedpolicy framework to govern network behavior, provide policy rules tocontrol plane function(s) to enforce policy rules, implement a front endto access subscription information relevant for policy decisions in auser data repository (UDR), and/or the like.

A network exposure function, NEF 125, may provide means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, receiveinformation from other network functions, and/or the like.

In an example, an network repository function, NRF 130 may supportservice discovery function that may receive NF discovery request from NFinstance, provide information about the discovered NF instances (bediscovered) to the NF instance, and maintain information about availableNF instances and their supported services, and/or the like.

In an example, an NSSF 120 may select a set of network slice instancesserving the UE 100, may determine allowed NSSAI. In an example, the NSSF120 may determine the AMF 155 set to be employed to serve the UE 100,and/or, based on configuration, determine a list of candidate AMF 155(s)155 by querying the NRF 130.

In an example, stored data in a UDR may include at least usersubscription data, including at least subscription identifiers, securitycredentials, access and mobility related subscription data, sessionrelated subscription data, policy data, and/or the like.

In an example, an AUSF 150 may support authentication server function(AUSF 150).

In an example, an application function, AF 145, may interact with the3GPP core network to provide services. In an example, based on operatordeployment, application functions may be trusted by the operator tointeract directly with relevant network functions. Application functionsnot allowed by the operator to access directly the network functions mayuse an external exposure framework (e.g., via the NEF 125) to interactwith relevant network functions.

In an example, control plane interface between the (R)AN 105 and the 5Gcore may support connection of multiple different kinds of AN(s) (e.g.3GPP RAN 105, N3IWF 170 for Un-trusted access 165) to the 5GC via acontrol plane protocol. In an example, an N2 AP protocol may be employedfor both the 3GPP access 105 and non-3GPP access 165. In an example,control plane interface between the (R)AN 105 and the 5G core maysupport decoupling between AMF 155 and other functions such as SMF 160that may need to control the services supported by AN(s) (e.g. controlof the UP resources in the AN 105 for a PDU session).

In an example, the 5GC may provide policy information from the PCF 135to the UE 100. In an example, the policy information may comprise:access network discovery and selection policy, UE 100 route selectionpolicy (URSP), SSC mode selection policy (SSCMSP), network sliceselection policy (NSSP), DNN selection policy, non-seamless offloadpolicy, and/or the like.

In an example, as depicted in example FIG. 5A and FIG. 5B, theregistration management, RM may be employed to register or de-register aUE/user 100 with the network, and establish the user context in thenetwork. Connection management may be employed to establish and releasethe signaling connection between the UE 100 and the AMF 155.

In an example, a UE 100 may register with the network to receiveservices that require registration. In an example, the UE 100 may updateits registration with the network periodically in order to remainreachable (periodic registration update), or upon mobility (e.g.,mobility registration update), or to update its capabilities or tore-negotiate protocol parameters.

In an example, an initial registration procedure as depicted in exampleFIG. 8 and FIG. 9 may involve execution of network access controlfunctions (e.g. user authentication and access authorization based onsubscription profiles in UDM 140). Example FIG. 9 is a continuation ofthe initial registration procedure depicted in FIG. 8. As a result ofthe initial registration procedure, the identity of the serving AMF 155may be registered in a UDM 140.

In an example, the registration management, RM procedures may beapplicable over both 3GPP access 105 and non 3GPP access 165.

An example FIG. 5A may depict the RM states of a UE 100 as observed bythe UE 100 and AMF 155. In an example embodiment, two RM states may beemployed in the UE 100 and the AMF 155 that may reflect the registrationstatus of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, andRM-REGISTERED 510. In an example, in the RM DEREGISTERED state 500, theUE 100 may not be registered with the network. The UE 100 context in theAMF 155 may not hold valid location or routing information for the UE100 so the UE 100 may not be reachable by the AMF 155. In an example,the UE 100 context may be stored in the UE 100 and the AMF 155. In anexample, in the RM REGISTERED state 510, the UE 100 may be registeredwith the network. In the RM-REGISTERED 510 state, the UE 100 may receiveservices that may require registration with the network.

In an example embodiment, two RM states may be employed in AMF 155 forthe UE 100 that may reflect the registration status of the UE 100 in theselected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As depicted in example FIG. 6A and FIG. 6B, connection management, CM,may comprise establishing and releasing a signaling connection between aUE 100 and an AMF 155 over N1 interface. The signaling connection may beemployed to enable NAS signaling exchange between the UE 100 and thecore network. The signaling connection between the UE 100 and the AMF155 may comprise both the AN signaling connection between the UE 100 andthe (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2connection for the UE 100 between the AN and the AMF 155.

As depicted in example FIG. 6A and FIG. 6B, two CM states may beemployed for the NAS signaling connectivity of the UE 100 with the AMF155, CM-IDLE 600, 620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600state may be in RM-REGISTERED 510 state and may have no NAS signalingconnection established with the AMF 155 over N1. The UE 100 may performcell selection, cell reselection, PLMN selection, and/or the like. A UE100 in CM-CONNECTED 610 state may have a NAS signaling connection withthe AMF 155 over N1.

In an example embodiment two CM states may be employed for the UE 100 atthe AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

In an example, an RRC inactive state may apply to NG-RAN (e.g. it mayapply to NR and E-UTRA connected to 5G CN). The AMF 155, based onnetwork configuration, may provide assistance information to the NG RAN105, to assist the NG RAN's 105 decision whether the UE 100 may be sentto RRC inactive state. When a UE 100 is CM-CONNECTED 610 with RRCinactive state, the UE 100 may resume the RRC connection due to uplinkdata pending, mobile initiated signaling procedure, as a response to RAN105 paging, to notify the network that it has left the RAN 105notification area, and/or the like.

In an example, a NAS signaling connection management may includeestablishing and releasing a NAS signaling connection. A NAS signalingconnection establishment function may be provided by the UE 100 and theAMF 155 to establish the NAS signaling connection for the UE 100 inCM-IDLE 600 state. The procedure of releasing the NAS signalingconnection may be initiated by the 5G (R)AN 105 node or the AMF 155.

In an example, reachability management of a UE 100 may detect whetherthe UE 100 is reachable and may provide the UE 100 location (e.g. accessnode) to the network to reach the UE 100. Reachability management may bedone by paging the UE 100 and the UE 100 location tracking. The UE 100location tracking may include both UE 100 registration area tracking andUE 100 reachability tracking. The UE 100 and the AMF 155 may negotiateUE 100 reachability characteristics in CM-IDLE 600, 620 state duringregistration and registration update procedures.

In an example, two UE 100 reachability categories may be negotiatedbetween a UE 100 and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100reachability allowing mobile device terminated data while the UE 100 isCM-IDLE 600 mode. 2) Mobile initiated connection only (MICO) mode. The5GC may support a PDU connectivity service that provides exchange ofPDUs between the UE 100 and a data network identified by a DNN. The PDUconnectivity service may be supported via PDU sessions that areestablished upon request from the UE 100.

In an example, a PDU session may support one or more PDU session types.PDU sessions may be established (e.g. upon UE 100 request), modified(e.g. upon UE 100 and 5GC request) and/or released (e.g. upon UE 100 and5GC request) using NAS SM signaling exchanged over N1 between the UE 100and the SMF 160. Upon request from an application server, the 5GC may beable to trigger a specific application in the UE 100. When receiving thetrigger, the UE 100 may send it to the identified application in the UE100. The identified application in the UE 100 may establish a PDUsession to a specific DNN.

In an example, the 5G QoS model may support a QoS flow based frameworkas depicted in example FIG. 7. The 5G QoS model may support both QoSflows that require a guaranteed flow bit rate and QoS flows that may notrequire a guaranteed flow bit rate. In an example, the 5G QoS model maysupport reflective QoS. The QoS model may comprise flow mapping orpacket marking at the UPF 110 (CN_UP) 110, AN 105 and/or the UE 100. Inan example, packets may arrive from and/or destined to theapplication/service layer 730 of UE 100, UPF 110 (CN_UP) 110, and/or theAF 145.

In an example, the QoS flow may be a granularity of QoS differentiationin a PDU session. A QoS flow ID, QFI, may be employed to identify theQoS flow in the 5G system. In an example, user plane traffic with thesame QFI within a PDU session may receive the same traffic forwardingtreatment. The QFI may be carried in an encapsulation header on N3and/or N9 (e.g. without any changes to the end-to-end packet header). Inan example, the QFI may be applied to PDUs with different types ofpayload. The QFI may be unique within a PDU session.

In an example, the QoS parameters of a QoS flow may be provided to the(R)AN 105 as a QoS profile over N2 at PDU session establishment, QoSflow establishment, or when NG-RAN is used at every time the user planeis activated. In an example, a default QoS rule may be required forevery PDU session. The SMF 160 may allocate the QFI for a QoS flow andmay derive QoS parameters from the information provided by the PCF 135.In an example, the SMF 160 may provide the QFI together with the QoSprofile containing the QoS parameters of a QoS flow to the (R)AN 105.

In an example, 5G QoS flow may be a granularity for QoS forwardingtreatment in the 5G system. Traffic mapped to the same 5G QoS flow mayreceive the same forwarding treatment (e.g. scheduling policy, queuemanagement policy, rate shaping policy, RLC configuration, and/or thelike). In an example, providing different QoS forwarding treatment ma5yrequire separate 5G QoS flows.

In an example, a 5G QoS indicator may be a scalar that may be employedas a reference to a specific QoS forwarding behavior (e.g. packet lossrate, packet delay budget) to be provided to a 5G QoS flow. In anexample, the 5G QoS indicator may be implemented in the access networkby the 5QI referencing node specific parameters that may control the QoSforwarding treatment (e.g. scheduling weights, admission thresholds,queue management thresholds, link layer protocol configuration, and/orthe like.).

In an example, 5GC may support edge computing and may enable operator(s)and 3rd party services to be hosted close to the UE's access point ofattachment. The 5G core network may select a UPF 110 close to the UE 100and may execute the traffic steering from the UPF 110 to the local datanetwork via a N6 interface. In an example, the selection and trafficsteering may be based on the UE's 100 subscription data, UE 100location, the information from application function AF 145, policy,other related traffic rules, and/or the like. In an example, the 5G corenetwork may expose network information and capabilities to an edgecomputing application function. The functionality support for edgecomputing may include local routing where the 5G core network may selecta UPF 110 to route the user traffic to the local data network, trafficsteering where the 5G core network may select the traffic to be routedto the applications in the local data network, session and servicecontinuity to enable UE 100 and application mobility, user planeselection and reselection, e.g. based on input from applicationfunction, network capability exposure where 5G core network andapplication function may provide information to each other via NEf 125,QoS and charging where PCF 135 may provide rules for QoS control andcharging for the traffic routed to the local data network, support oflocal area data network where 5G core network may provide support toconnect to the LADN in a certain area where the applications aredeployed, and/or the like.

An example 5G system may be a 3GPP system comprising of 5G accessnetwork 105, 5G core network and a UE 100, and/or the like. AllowedNSSAI may be an NSSAI provided by a serving PLMN during e.g. aregistration procedure, indicating the NSSAI allowed by the network forthe UE 100 in the serving PLMN for the current registration area.

In an example, a PDU connectivity service may provide exchange of PDUsbetween a UE 100 and a data network. A PDU session may be an associationbetween the UE 100 and the data network, DN 115, that may provide thePDU connectivity service. The type of association may be IP, Ethernetand/or unstructured.

Establishment of user plane connectivity to a data network via networkslice instance(s) may comprise the following: performing a RM procedureto select an AMF 155 that supports the required network slices andestablishing one or more PDU session(s) to the required data network viathe network slice instance(s).

In an example, the set of network slices for a UE 100 may be changed atany time while the UE 100 may be registered with the network, and may beinitiated by the network, or the UE 100.

In an example, a periodic registration update may be UE 100re-registration at expiry of a periodic registration timer. A requestedNSSAI may be a NSSAI that the UE 100 may provide to the network.

In an example, a service based interface may represent how a set ofservices may be provided/exposed by a given NF.

In an example, a service continuity may be an uninterrupted userexperience of a service, including the cases where the IP address and/oranchoring point may change. In an example, a session continuity mayrefer to continuity of a PDU session. For PDU session of IP type sessioncontinuity may imply that the IP address is preserved for the lifetimeof the PDU session. An uplink classifier may be a UPF 110 functionalitythat aims at diverting uplink traffic, based on filter rules provided bythe SMF 160, towards data network, DN 115.

In an example, the 5G system architecture may support data connectivityand services enabling deployments to use techniques such as e.g. networkfunction virtualization and/or software defined networking. The 5Gsystem architecture may leverage service-based interactions betweencontrol plane (CP) network functions where identified. In 5G systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A 5G system may enable anetwork function to interact with other NF(s) directly if required.

In an example, the 5G system may reduce dependencies between the accessnetwork (AN) and the core network (CN). The architecture may comprise aconverged access-agnostic core network with a common AN - CN interfacewhich may integrate different 3GPP and non-3GPP access types.

In an example, the 5G system may support a unified authenticationframework, stateless NFs, where the compute resource is decoupled fromthe storage resource, capability exposure, and concurrent access tolocal and centralized services. To support low latency services andaccess to local data networks, UP functions may be deployed close to theaccess network.

In an example, the 5G system may support roaming with home routedtraffic and/or local breakout traffic in the visited PLMN. An example 5Garchitecture may be service-based and the interaction between networkfunctions may be represented in two ways. (1) As service-basedrepresentation (depicted in example FIG. 1), where network functionswithin the control plane, may enable other authorized network functionsto access their services. This representation may also includepoint-to-point reference points where necessary. (2) Reference pointrepresentation, showing the interaction between the NF services in thenetwork functions described by point-to-point reference point (e.g. N11)between any two network functions.

In an example, a network slice may comprise the core network controlplane and user plane network functions, the 5G Radio Access Network; theN3IWF functions to the non-3GPP Access Network, and/or the like. Networkslices may differ for supported features and network functionimplementation. The operator may deploy multiple network slice instancesdelivering the same features but for different groups of UEs, e.g. asthey deliver a different committed service and/or because they may bededicated to a customer. The NSSF 120 may store the mapping informationbetween slice instance ID and NF ID (or NF address).

In an example, a UE 100 may simultaneously be served by one or morenetwork slice instances via a 5G-AN. In an example, the UE 100 may beserved by k network slices (e.g. k=8, 16, etc) at a time. An AMF 155instance serving the UE 100 logically may belong to a network sliceinstance serving the UE 100.

In an example, a PDU session may belong to one specific network sliceinstance per PLMN. In an example, different network slice instances maynot share a PDU session. Different slices may have slice-specific PDUsessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) mayidentify a network slice. An S-NSSAI may comprise a slice/service type(SST), which may refer to the expected network slice behavior in termsof features and services; and/or a slice differentiator (SD). A slicedifferentiator may be optional information that may complement theslice/service type(s) to allow further differentiation for selecting anetwork slice instance from potentially multiple network slice instancesthat comply with the indicated slice/service type. In an example, thesame network slice instance may be selected employing differentS-NSSAIs. The CN part of a network slice instance(s) serving a UE 100may be selected by CN.

In an example, subscription data may include the S-NSSAI(s) of thenetwork slices that the UE 100 subscribes to. One or more S-NSSAIs maybe marked as default S-NSSAI. In an example, k S-NSSAI may be markeddefault S-NSSAI (e.g. k=8, 16, etc.). In an example, the UE 100 maysubscribe to more than 8 S-NSSAIs.

In an example, a UE 100 may be configured by the HPLMN with a configuredNSSAI per PLMN. Upon successful completion of a UE's registrationprocedure, the UE 100 may obtain from the AMF 155 an Allowed NSSAI forthis PLMN, which may include one or more S-NSSAIs.

In an example, the Allowed NSSAI may take precedence over the configuredNSSAI for a PLMN. The UE 100 may use the S-NSSAIs in the allowed NSSAIcorresponding to a network slice for the subsequent network sliceselection related procedures in the serving PLMN.

In an example, the establishment of user plane connectivity to a datanetwork via a network slice instance(s) may comprise: performing a RMprocedure to select an AMF 155 that may support the required networkslices, establishing one or more PDU sessions to the required datanetwork via the network slice instance(s), and/or the like.

In an example, when a UE 100 registers with a PLMN, if the UE 100 forthe PLMN has a configured NSSAI or an allowed NSSAI, the UE 100 mayprovide to the network in RRC and NAS layer a requested NSSAI comprisingthe S-NSSAI(s) corresponding to the slice(s) to which the UE 100attempts to register, a temporary user ID if one was assigned to the UE,and/or the like. The requested NSSAI may be configured-NSSAI,allowed-NSSAI, and/or the like.

In an example, when a UE 100 registers with a PLMN, if for the PLMN theUE 100 has no configured NSSAI or allowed NSSAI, the RAN 105 may routeNAS signaling from/to the UE 100 to/from a default AMF 155.

In an example, the network, based on local policies, subscriptionchanges and/or UE 100 mobility, may change the set of permitted networkslice(s) to which the UE 100 is registered. In an example, the networkmay perform the change during a registration procedure or trigger anotification towards the UE 100 of the change of the supported networkslices using an RM procedure (which may trigger a registrationprocedure). The network may provide the UE 100 with a new allowed NSSAIand tracking area list.

In an example, during a registration procedure in a PLMN, in case thenetwork decides that the UE 100 may be served by a different AMF 155based on network slice(s) aspects, the AMF 155 that first received theregistration request may redirect the registration request to anotherAMF 155 via the RAN 105 or via direct signaling between the initial AMF155 and the target AMF 155.

In an example, the network operator may provision the UE 100 withnetwork slice selection policy (NSSP). The NSSP may comprise one or moreNSSP rules.

In an example, if a UE 100 has one or more PDU sessions establishedcorresponding to the a specific S-NSSAI, the UE 100 may route the userdata of the application in one of the PDU sessions, unless otherconditions in the UE 100 may prohibit the use of the PDU sessions. Ifthe application provides a DNN, then the UE 100 may consider the DNN todetermine which PDU session to use. In an example, if the UE 100 doesnot have a PDU session established with the specific S-NSSAI, the UE 100may request a new PDU session corresponding to the S-NSSAI and with theDNN that may be provided by the application. In an example, in order forthe RAN 105 to select a proper resource for supporting network slicingin the RAN 105, the RAN 105 may be aware of the network slices used bythe UE 100.

In an example, an AMF 155 may select an SMF 160 in a network sliceinstance based on S-NSSAI, DNN and/or other information e.g. UE 100subscription and local operator policies, and/or the like, when the UE100 triggers the establishment of a PDU session. The selected SMF 160may establish the PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of sliceinformation for the slices the UE 100 may access, when the UE 100 isaware or configured that privacy considerations may apply to NSSAI, theUE 100 may not include NSSAI in NAS signaling unless the UE 100 has aNAS security context and the UE 100 may not include NSSAI in unprotectedRRC signaling.

In an example, for roaming scenarios, the network slice specific networkfunctions in VPLMN and HPLMN may be selected based on the S-NSSAIprovided by the UE 100 during PDU connection establishment. If astandardized S-NSSAI is used, selection of slice specific NF instancesmay be done by one or more PLMN(s) based on the provided S-NSSAI. In anexample, the VPLMN may map the S-NSSAI of HPLMN to a S-NSSAI of VPLMNbased on roaming agreement (e.g., including mapping to a default S-NSSAIof VPLMN). In an example, the selection of slice specific NF instance inVPLMN may be done based on the S-NSSAI of VPLMN. In an example, theselection of any slice specific NF instance in HPLMN may be based on theS-NSSAI of HPLMN.

As depicted in example FIG. 8 and FIG. 9, a registration procedure maybe performed by the UE 100 to get authorized to receive services, toenable mobility tracking, to enable reachability, and/or the like.

In an example, the UE 100 may send to the (R)AN 105 an AN message 805(comprising AN parameters, RM-NAS registration request (registrationtype, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), securityparameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GCcapability, PDU session status, PDU session(s) to be re-activated,Follow on request, MICO mode preference, and/or the like), and/or thelike). In an example, in case of NG-RAN, the AN parameters may includee.g. SUCI or SUPI or the 5G-GUTI, the Selected PLMN ID and requestedNSSAI, and/or the like. In an example, the AN parameters may compriseestablishment cause. The establishment cause may provide the reason forrequesting the establishment of an RRC connection. In an example, theregistration type may indicate if the UE 100 wants to perform an initialregistration (i.e. the UE 100 is in RM-DEREGISTERED state), a mobilityregistration update (e.g., the UE 100 is in RM-REGISTERED state andinitiates a registration procedure due to mobility), a periodicregistration update (e.g., the UE 100 is in RM-REGISTERED state and mayinitiate a registration procedure due to the periodic registrationupdate timer expiry) or an emergency registration (e.g., the UE 100 isin limited service state). In an example, if the UE 100 performing aninitial registration (i.e., the UE 100 is in RM-DEREGISTERED state) to aPLMN for which the UE 100 does not already have a 5G-GUTI, the UE 100may include its SUCI or SUPI in the registration request. The SUCI maybe included if the home network has provisioned the public key toprotect SUPI in the UE. If the UE 100 received a UE 100 configurationupdate command indicating that the UE 100 needs to re-register and the5G-GUTI is invalid, the UE 100 may perform an initial registration andmay include the SUPI in the registration request message. For anemergency registration, the SUPI may be included if the UE 100 does nothave a valid 5G-GUTI available; the PEI may be included when the UE 100has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI may beincluded and it may indicate the last serving AMF 155. If the UE 100 isalready registered via a non-3GPP access in a PLMN different from thenew PLMN (e.g., not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the 3GPP access, the UE 100 may not provide over the3GPP access the 5G-GUTI allocated by the AMF 155 during the registrationprocedure over the non-3GPP access. If the UE 100 is already registeredvia a 3GPP access in a PLMN (e.g., the registered PLMN), different fromthe new PLMN (i.e. not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the non-3GPP access, the UE 100 may not provide overthe non-3GPP access the 5G-GUTI allocated by the AMF 155 during theregistration procedure over the 3GPP access. The UE 100 may provide theUE's usage setting based on its configuration. In case of initialregistration or mobility registration update, the UE 100 may include themapping of requested NSSAI, which may be the mapping of one or moreS-NSSAI of the requested NSSAI to the S-NSSAIs of the configured NSSAIfor the HPLMN, to ensure that the network is able to verify whether theS-NSSAI(s) in the requested NSSAI are permitted based on the subscribedS-NSSAIs. If available, the last visited TAI may be included in order tohelp the AMF 155 produce registration area for the UE. In an example,the security parameters may be used for authentication and integrityprotection. requested NSSAI may indicate the network slice selectionassistance information. The PDU session status may indicates thepreviously established PDU sessions in the UE. When the UE 100 isconnected to the two AMF 155 belonging to different PLMN via 3GPP accessand non-3GPP access then the PDU session status may indicate theestablished PDU session of the current PLMN in the UE. The PDUsession(s) to be re-activated may be included to indicate the PDUsession(s) for which the UE 100 may intend to activate UP connections. APDU session corresponding to a LADN may not be included in the PDUsession(s) to be re-activated when the UE 100 is outside the area ofavailability of the LADN. The follow on request may be included when theUE 100 may have pending uplink signaling and the UE 100 may not includePDU session(s) to be re-activated, or the registration type may indicatethe UE 100 may want to perform an emergency registration.

In an example, if a SUPI is included or the 5G-GUTI does not indicate avalid AMF 155, the (R)AN 105, based on (R)AT and requested NSSAI, ifavailable, may selects 808 an AMF 155. If UE 100 is in CM-CONNECTEDstate, the (R)AN 105 may forward the registration request message to theAMF 155 based on the N2 connection of the UE. If the (R)AN 105 may notselect an appropriate AMF 155, it may forward the registration requestto an AMF 155 which has been configured, in (R)AN 105, to perform AMF155 selection 808.

In an example, the (R)AN 105 may send to the new AMF 155 an N2 message810 (comprising: N2 parameters, RM-NAS registration request(registration type, SUPI or 5G-GUTI, last visited TAI (if available),security parameters, requested NSSAI, mapping of requested NSSAI, UE 1005GC capability, PDU session status, PDU session(s) to be re-activated,follow on request, and MICO mode preference), and/or the like). In anexample, when NG-RAN is used, the N2 parameters may comprise theselected PLMN ID, location information, cell identity and the RAT typerelated to the cell in which the UE 100 is camping. In an example, whenNG-RAN is used, the N2 parameters may include the establishment cause.

In an example, the new AMF 155 may send to the old AMF 155 anNamf_Communication_UEContextTransfer (complete registration request)815. In an example, if the UE's 5G-GUTI was included in the registrationrequest and the serving AMF 155 has changed since last registrationprocedure, the new AMF 155 may invoke theNamf_Communication_UEContextTransfer service operation 815 on the oldAMF 155 including the complete registration request IE, which may beintegrity protected, to request the UE's SUPI and MM Context. The oldAMF 155 may use the integrity protected complete registration request IEto verify if the context transfer service operation invocationcorresponds to the UE 100 requested. In an example, the old AMF 155 maytransfer the event subscriptions information by one or more NF consumer,for the UE, to the new AMF 155. In an example, if the UE 100 identifiesitself with PEI, the SUPI request may be skipped.

In an example, the old AMF 155 may send to new AMF 155 a response 815 toNamf_Communication_UEContextTransfer (SUPI, MM context, SMF 160information, PCF ID). In an example, the old AMF 155 may respond to thenew AMF 155 for the Namf_Communication_UEContextTransfer invocation byincluding the UE's SUPI and MM context. In an example, if old AMF 155holds information about established PDU sessions, the old AMF 155 mayinclude SMF 160 information including S-NSSAI(s), SMF 160 identities andPDU session ID. In an example, if old AMF 155 holds information aboutactive NGAP UE-TNLA bindings to N3IWF, the old AMF 155 may includeinformation about the NGAP UE-TNLA bindings.

In an example, if the SUPI is not provided by the UE 100 nor retrievedfrom the old AMF 155 the identity request procedure 820 may be initiatedby the AMF 155 sending an identity request message to the UE 100requesting the SUCI.

In an example, the UE 100 may respond with an identity response message820 including the SUCI. The UE 100 may derive the SUCI by using theprovisioned public key of the HPLMN.

In an example, the AMF 155 may decide to initiate UE 100 authentication825 by invoking an AUSF 150. The AMF 155 may select an AUSF 150 based onSUPI or SUCI. In an example, if the AMF 155 is configured to supportemergency registration for unauthenticated SUPIs and the UE 100indicated registration type emergency registration the AMF 155 may skipthe authentication and security setup or the AMF 155 may accept that theauthentication may fail and may continue the registration procedure.

In an example, the authentication 830 may be performed byNudm_UEAuthenticate_Get operation. The AUSF 150 may discover a UDM 140.In case the AMF 155 provided a SUCI to AUSF 150, the AUSF 150 may returnthe SUPI to AMF 155 after the authentication is successful. In anexample, if network slicing is used, the AMF 155 may decide if theregistration request needs to be rerouted where the initial AMF 155refers to the AMF 155. In an example, the AMF 155 may initiate NASsecurity functions. In an example, upon completion of NAS securityfunction setup, the AMF 155 may initiate NGAP procedure to enable 5G-ANuse it for securing procedures with the UE. In an example, the 5G-AN maystore the security context and may acknowledge to the AMF 155. The 5G-ANmay use the security context to protect the messages exchanged with theUE.

In an example, new AMF 155 may send to the old AMF 155Namf_Communication_RegistrationCompleteNotify 835. If the AMF 155 haschanged, the new AMF 155 may notify the old AMF 155 that theregistration of the UE 100 in the new AMF 155 may be completed byinvoking the Namf_Communication_RegistrationCompleteNotify serviceoperation. If the authentication/security procedure fails, then theregistration may be rejected, and the new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operation with areject indication reason code towards the old AMF 155. The old AMF 155may continue as if the UE 100 context transfer service operation wasnever received. If one or more of the S-NSSAIs used in the oldregistration area may not be served in the target registration area, thenew AMF 155 may determine which PDU session may not be supported in thenew registration area. The new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operationincluding the rejected PDU session ID and a reject cause (e.g. theS-NSSAI becomes no longer available) towards the old AMF 155. The newAMF 155 may modify the PDU session status correspondingly. The old AMF155 may inform the corresponding SMF 160(s) to locally release the UE'sSM context by invoking the Nsmf_PDUSession_ReleaseSMContext serviceoperation.

In an example, the new AMF 155 may send to the UE 100 an identityrequest/response 840 (e.g., PEI). If the PEI was not provided by the UE100 nor retrieved from the old AMF 155, the identity request proceduremay be initiated by AMF 155 sending an identity request message to theUE 100 to retrieve the PEI. The PEI may be transferred encrypted unlessthe UE 100 performs emergency registration and may not be authenticated.For an emergency registration, the UE 100 may have included the PEI inthe registration request.

In an example, the new AMF 155 may initiate ME identity check 845 byinvoking the N5g-eir_EquipmentldentityCheck_Get service operation 845.

In an example, the new AMF 155, based on the SUPI, may select 905 a UDM140. The UDM 140 may select a UDR instance. In an example, the AMF 155may selects a UDM 140.

In an example, if the AMF 155 has changed since the last registrationprocedure, or if the UE 100 provides a SUPI which may not refer to avalid context in the AMF 155, or if the UE 100 registers to the same AMF155 it has already registered to a non-3GPP access (e.g., the UE 100 isregistered over a non-3GPP access and may initiate the registrationprocedure to add a 3GPP access), the new AMF 155 may register with theUDM 140 using Nudm_UECM_Registration 910 and may subscribe to benotified when the UDM 140 may deregister the AMF 155. The UDM 140 maystore the AMF 155 identity associated to the access type and may notremove the AMF 155 identity associated to the other access type. The UDM140 may store information provided at registration in UDR, byNudr_UDM_Update. In an example, the AMF 155 may retrieve the access andmobility subscription data and SMF 160 selection subscription data usingNudm_SDM_Get 915. The UDM 140 may retrieve this information from UDR byNudr_UDM_Query(access and mobility subscription data). After asuccessful response is received, the AMF 155 may subscribe to benotified using Nudm_SDM_Subscribe 920 when the data requested may bemodified. The UDM 140 may subscribe to UDR by Nudr_UDM_Subscribe. TheGPSI may be provided to the AMF 155 in the subscription data from theUDM 140 if the GPSI is available in the UE 100 subscription data. In anexample, the new AMF 155 may provide the access type it serves for theUE 100 to the UDM 140 and the access type may be set to 3GPP access. TheUDM 140 may store the associated access type together with the servingAMF 155 in UDR by Nudr_UDM_Update. The new AMF 155 may create an MMcontext for the UE 100 after getting the mobility subscription data fromthe UDM 140. In an example, when the UDM 140 stores the associatedaccess type together with the serving AMF 155, the UDM 140 may initiatea Nudm_UECM_DeregistrationNotification 921 to the old AMF 155corresponding to 3GPP access. The old AMF 155 may remove the MM contextof the UE. If the serving NF removal reason indicated by the UDM 140 isinitial registration, then the old AMF 155 may invoke theNamf_EventExposure_Notify service operation towards all the associatedSMF 160 s of the UE 100 to notify that the UE 100 is deregistered fromold AMF 155. The SMF 160 may release the PDU session(s) on getting thisnotification. In an example, the old AMF 155 may unsubscribe with theUDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

In an example, if the AMF 155 decides to initiate PCF 135 communication,e.g. the AMF 155 has not yet obtained access and mobility policy for theUE 100 or if the access and mobility policy in the AMF 155 are no longervalid, the AMF 155 may select 925 a PCF 135. If the new AMF 155 receivesa PCF ID from the old AMF 155 and successfully contacts the PCF 135identified by the PCF ID, the AMF 155 may select the (V-)PCF identifiedby the PCF ID.

If the PCF 135 identified by the PCF ID may not be used (e.g. noresponse from the PCF 135) or if there is no PCF ID received from theold AMF 155, the AMF 155 may select 925 a PCF 135.

In an example, the new AMF 155 may perform a policy associationestablishment 930 during registration procedure. If the new AMF 155contacts the PCF 135 identified by the (V-) PCF ID received duringinter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in theNpcf AMPolicyControl Get operation. If the AMF 155 notifies the mobilityrestrictions (e.g. UE 100 location) to the PCF 135 for adjustment, or ifthe PCF 135 updates the mobility restrictions itself due to someconditions (e.g. application in use, time and date), the PCF 135 mayprovide the updated mobility restrictions to the AMF 155.

In an example, the PCF 135 may invoke Namf_EventExposure_Subscribeservice operation 935 for UE 100 event subscription.

In an example, the AMF 155 may send to the SMF 160 an NsmfPDUSession_UpdateSMContext 936. In an example, the AMF 155 may invokethe Nsmf PDUSession_UpdateSMContext if the PDU session(s) to bere-activated is included in the registration request. The AMF 155 maysend Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associatedwith the PDU session(s) to activate user plane connections of the PDUsession(s). The SMF 160 may decide to trigger e.g. the intermediate UPF110 insertion, removal or change of PSA. In the case that theintermediate UPF 110 insertion, removal, or relocation is performed forthe PDU session(s) not included in PDU session(s) to be re-activated,the procedure may be performed without N11 and N2 interactions to updatethe N3 user plane between (R)AN 105 and SGC. The AMF 155 may invoke theNsmf PDUSession_ReleaseSMContext service operation towards the SMF 160if any PDU session status indicates that it is released at the UE 100.The AMF 155 may invoke the Nsmf PDUSession_ReleaseSMContext serviceoperation towards the SMF 160 in order to release any network resourcesrelated to the PDU session.

In an example, the new AMF 155155 may send to a N3IWF an N2 AMF 155mobility request 940. If the AMF 155 has changed, the new AMF 155 maycreate an NGAP UE 100 association towards the N3IWF to which the UE 100is connected. In an example, the N3IWF may respond to the new AMF 155with an N2 AMF 155 mobility response 940.

In an example, the new AMF 155 may send to the UE 100 a registrationaccept 955 (comprising: 5G-GUTI, registration area, mobilityrestrictions, PDU session status, allowed NSSAI, [mapping of allowedNSSAI], periodic registration update timer, LADN information andaccepted MICO mode, IMS voice over PS session supported indication,emergency service support indicator, and/or the like). In an example,the AMF 155 may send the registration accept message to the UE 100indicating that the registration request has been accepted. 5G-GUTI maybe included if the AMF 155 allocates a new 5G-GUTI. If the AMF 155allocates a new registration area, it may send the registration area tothe UE 100 via registration accept message 955. If there is noregistration area included in the registration accept message, the UE100 may consider the old registration area as valid. In an example,mobility restrictions may be included in case mobility restrictions mayapply for the UE 100 and registration type may not be emergencyregistration. The AMF 155 may indicate the established PDU sessions tothe UE 100 in the PDU session status. The UE 100 may remove locally anyinternal resources related to PDU sessions that are not marked asestablished in the received PDU session status. In an example, when theUE 100 is connected to the two AMF 155 belonging to different PLMN via3GPP access and non-3GPP access then the UE 100 may remove locally anyinternal resources related to the PDU session of the current PLMN thatare not marked as established in received PDU session status. If the PDUsession status information was in the registration request, the AMF 155may indicate the PDU session status to the UE. The mapping of allowedNSSAI may be the mapping of one or more S-NSSAI of the allowed NSSAI tothe S-NSSAIs of the configured NSSAI for the HPLMN. The AMF 155 mayinclude in the registration accept message 955 the LADN information forLADNs that are available within the registration area determined by theAMF 155 for the UE. If the UE 100 included MICO mode in the request,then AMF 155 may respond whether MICO mode may be used. The AMF 155 mayset the IMS voice over PS session supported Indication. In an example,in order to set the IMS voice over PS session supported indication, theAMF 155 may perform a UE/RAN radio information and compatibility requestprocedure to check the compatibility of the UE 100 and RAN radiocapabilities related to IMS voice over PS. In an example, the emergencyservice support indicator may inform the UE 100 that emergency servicesare supported, e.g., the UE 100 may request PDU session for emergencyservices. In an example, the handover restriction list and UE-AMBR maybe provided to NG-RAN by the AMF 155.

In an example, the UE 100 may send to the new AMF 155 a registrationcomplete 960 message. In an example, the UE 100 may send theregistration complete message 960 to the AMF 155 to acknowledge that anew 5G-GUTI may be assigned. In an example, when information about thePDU session(s) to be re-activated is not included in the registrationrequest, the AMF 155 may release the signaling connection with the UE100. In an example, when the follow-on request is included in theregistration request, the AMF 155 may not release the signalingconnection after the completion of the registration procedure. In anexample, if the AMF 155 is aware that some signaling is pending in theAMF 155 or between the UE 100 and the SGC, the AMF 155 may not releasethe signaling connection after the completion of the registrationprocedure.

As depicted in example FIG. 10 and FIG. 11, a service request proceduree.g., a UE 100 triggered service request procedure may be used by a UE100 in CM-IDLE state to request the establishment of a secure connectionto an AMF 155. FIG. 11 is continuation of FIG. 10 depicting the servicerequest procedure. The service request procedure may be used to activatea user plane connection for an established PDU session. The servicerequest procedure may be triggered by the UE 100 or the SGC, and may beused when the UE 100 is in CM-IDLE and/or in CM-CONNECTED and may allowselectively to activate user plane connections for some of theestablished PDU sessions.

In an example, a UE 100 in CM IDLE state may initiate the servicerequest procedure to send uplink signaling messages, user data, and/orthe like, as a response to a network paging request, and/or the like. Inan example, after receiving the service request message, the AMF 155 mayperform authentication. In an example, after the establishment ofsignaling connection to the AMF 155, the UE 100 or network may sendsignaling messages, e.g. PDU session establishment from the UE 100 to aSMF 160, via the AMF 155.

In an example, for any service request, the AMF 155 may respond with aservice accept message to synchronize PDU session status between the UE100 and network. The AMF 155 may respond with a service reject messageto the UE 100, if the service request may not be accepted by thenetwork. The service reject message may include an indication or causecode requesting the UE 100 to perform a registration update procedure.In an example, for service request due to user data, network may takefurther actions if user plane connection activation may not besuccessful. In an example FIG. 10 and FIG. 11, more than one UPF, e.g.,old UPF 110-2 and PDU session Anchor PSA UPF 110-3 may be involved.

In an example, the UE 100 may send to a (R)AN 105 an AN messagecomprising AN parameters, mobility management, MM NAS service request1005 (e.g., list of PDU sessions to be activated, list of allowed PDUsessions, security parameters, PDU session status, and/or the like),and/or the like. In an example, the UE 100 may provide the list of PDUsessions to be activated when the UE 100 may re-activate the PDUsession(s). The list of allowed PDU sessions may be provided by the UE100 when the service request may be a response of a paging or a NASnotification, and may identify the PDU sessions that may be transferredor associated to the access on which the service request may be sent. Inan example, for the case of NG-RAN, the AN parameters may includeselected PLMN ID, and an establishment cause. The establishment causemay provide the reason for requesting the establishment of an RRCconnection. The UE 100 may send NAS service request message towards theAMF 155 encapsulated in an RRC message to the RAN 105.

In an example, if the service request may be triggered for user data,the UE 100 may identify, using the list of PDU sessions to be activated,the PDU session(s) for which the UP connections are to be activated inthe NAS service request message. If the service request may be triggeredfor signaling, the UE 100 may not identify any PDU session(s). If thisprocedure may be triggered for paging response, and/or the UE 100 mayhave at the same time user data to be transferred, the UE 100 mayidentify the PDU session(s) whose UP connections may be activated in MMNAS service request message, by the list of PDU sessions to beactivated.

In an example, if the service request over 3GPP access may be triggeredin response to a paging indicating non-3GPP access, the NAS servicerequest message may identify in the list of allowed PDU sessions thelist of PDU sessions associated with the non-3GPP access that may bere-activated over 3GPP. In an example, the PDU session status mayindicate the PDU sessions available in the UE 100. In an example, the UE100 may not trigger the service request procedure for a PDU sessioncorresponding to a LADN when the UE 100 may be outside the area ofavailability of the LADN. The UE 100 may not identify such PDUsession(s) in the list of PDU sessions to be activated, if the servicerequest may be triggered for other reasons.

In an example, the (R)AN 105 may send to AMF 155 an N2 Message 1010(e.g., a service request) comprising N2 parameters, MM NAS servicerequest, and/or the like. The AMF 155 may reject the N2 message if itmay not be able to handle the service request. In an example, if NG-RANmay be used, the N2 parameters may include the 5G-GUTI, selected PLMNID, location information, RAT type, establishment cause, and/or thelike. In an example, the 5G-GUTI may be obtained in RRC procedure andthe (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In anexample, the location information and RAT type may relate to the cell inwhich the UE 100 may be camping. In an example, based on the PDU sessionstatus, the AMF 155 may initiate PDU session release procedure in thenetwork for the PDU sessions whose PDU session ID(s) may be indicated bythe UE 100 as not available.

In an example, if the service request was not sent integrity protectedor integrity protection verification failed, the AMF 155 may initiate aNAS authentication/security procedure 1015.

In an example, if the UE 100 triggers the service request to establish asignaling connection, upon successful establishment of the signalingconnection, the UE 100 and the network may exchange NAS signaling.

In an example the AMF 155 may send to the SMF 160 a PDU session updatecontext request 1020 e.g., Nsmf PDUSession_UpdateSMContext requestcomprising PDU session ID(s), Cause(s), UE 100 location information,access type, and/or the like.

In an example, the Nsmf_PDUSession_UpdateSMContext request may beinvoked by the AMF 155 if the UE 100 may identify PDU session(s) to beactivated in the NAS service request message. In an example, the NsmfPDUSession_UpdateSMContext request may be triggered by the SMF 160wherein the PDU session(s) identified by the UE 100 may correlate toother PDU session ID(s) than the one triggering the procedure. In anexample, the Nsmf PDUSession_UpdateSMContext request may be triggered bythe SMF 160 wherein the current UE 100 location may be outside the areaof validity for the N2 information provided by the SMF 160 during anetwork triggered service request procedure. The AMF 155 may not sendthe N2 information provided by the SMF 160 during the network triggeredservice request procedure.

In an example, the AMF 155 may determine the PDU session(s) to beactivated and may send an Nsmf PDUSession_UpdateSMContext request to SMF160(s) associated with the PDU session(s) with cause set to indicateestablishment of user plane resources for the PDU session(s).

In an example, if the procedure may be triggered in response to pagingindicating non-3GPP access, and the list of allowed PDU sessionsprovided by the UE 100 may not include the PDU session for which the UE100 was paged, the AMF 155 may notify the SMF 160 that the user planefor the PDU session may not be re-activated. The service requestprocedure may succeed without re-activating the user plane of any PDUsessions, and the AMF 155 may notify the UE 100.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) keep thePDU session, may reject the activation of user plane connection for thePDU session and may inform the AMF 155. In an example, if the proceduremay be triggered by a network triggered service request, the SMF 160 maynotify the UPF 110 that originated the data notification to discarddownlink data for the PDU sessions and/or to not provide further datanotification messages. The SMF 160 may respond to the AMF 155 with anappropriate reject cause and the user plane activation of PDU sessionmay be stopped.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) release thePDU session. The SMF 160 may locally release the PDU session and mayinform the AMF 155 that the PDU session may be released. The SMF 160 mayrespond to the AMF 155 with an appropriate reject cause and the userplane Activation of PDU session may be stopped.

In an example, if the UP activation of the PDU session may be acceptedby the SMF 160, based on the location info received from the AMF 155,the SMF 160 may check the UPF 110 Selection 1025 Criteria (e.g., sliceisolation requirements, slice coexistence requirements, UPF's 110dynamic load, UPF's 110 relative static capacity among UPFs supportingthe same DNN, UPF 110 location available at the SMF 160, UE 100 locationinformation, Capability of the UPF 110 and the functionality requiredfor the particular UE 100 session. In an example, an appropriate UPF 110may be selected by matching the functionality and features required fora UE 100, DNN, PDU session type (i.e. IPv4, IPv6, ethernet type orunstructured type) and if applicable, the static IP address/prefix, SSCmode selected for the PDU session, UE 100 subscription profile in UDM140, DNAI as included in the PCC rules, local operator policies,S-NSSAI, access technology being used by the UE 100, UPF 110 logicaltopology, and/or the like), and may determine to perform one or more ofthe following: continue using the current UPF(s); may select a newintermediate UPF 110 (or add/remove an intermediate UPF 110), if the UE100 has moved out of the service area of the UPF 110 that was previouslyconnecting to the (R)AN 105, while maintaining the UPF(s) acting as PDUsession anchor; may trigger re-establishment of the PDU session toperform relocation/reallocation of the UPF 110 acting as PDU sessionanchor, e.g. the UE 100 has moved out of the service area of the anchorUPF 110 which is connecting to RAN 105.

In an example, the SMF 160 may send to the UPF 110 (e.g., newintermediate UPF 110) an N4 session establishment request 1030. In anexample, if the SMF 160 may select a new UPF 110 to act as intermediateUPF 110-2 for the PDU session, or if the SMF 160 may select to insert anintermediate UPF 110 for a PDU session which may not have anintermediate UPF 110-2, an N4 session establishment request 1030 messagemay be sent to the new UPF 110, providing packet detection, dataforwarding, enforcement and reporting rules to be installed on the newintermediate UPF. The PDU session anchor addressing information (on N9)for this PDU session may be provided to the intermediate UPF 110-2.

In an example, if a new UPF 110 is selected by the SMF 160 to replacethe old (intermediate) UPF 110-2, the SMF 160 may include a dataforwarding indication. The data forwarding indication may indicate tothe UPF 110 that a second tunnel endpoint may be reserved for bufferedDL data from the old I-UPF.

In an example, the new UPF 110 (intermediate) may send to SMF 160 an N4session establishment response message 1030. In case the UPF 110 mayallocate CN tunnel info, the UPF 110 may provide DL CN tunnel info forthe UPF 110 acting as PDU session anchor and UL CN tunnel info (e.g., CNN3 tunnel info) to the SMF 160. If the data forwarding indication may bereceived, the new (intermediate) UPF 110 acting as N3 terminating pointmay send DL CN tunnel info for the old (intermediate) UPF 110-2 to theSMF 160. The SMF 160 may start a timer, to release the resource in theold intermediate UPF 110-2.

In an example, if the SMF 160 may selects a new intermediate UPF 110 forthe PDU session or may remove the old I-UPF 110-2, the SMF 160 may sendN4 session modification request message 1035 to PDU session anchor, PSAUPF 110-3, providing the data forwarding indication and DL tunnelinformation from new intermediate UPF 110.

In an example, if the new intermediate UPF 110 may be added for the PDUsession, the (PSA) UPF 110-3 may begin to send the DL data to the newI-UPF 110 as indicated in the DL tunnel information.

In an example, if the service request may be triggered by the network,and the SMF 160 may remove the old I-UPF 110-2 and may not replace theold I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include the dataforwarding indication in the request. The data forwarding indication mayindicate to the (PSA) UPF 110-3 that a second tunnel endpoint may bereserved for buffered DL data from the old I-UPF 110-2. In this case,the PSA UPF 110-3 may begin to buffer the DL data it may receive at thesame time from the N6 interface.

In an example, the PSA UPF 110-3 (PSA) may send to the SMF 160 an N4session modification response 1035. In an example, if the dataforwarding indication may be received, the PSA UPF 110-3 may become asN3 terminating point and may send CN DL tunnel info for the old(intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer,to release the resource in old intermediate UPF 110-2 if there is one.

In an example, the SMF 160 may send to the old UPF 110-2 an N4 sessionmodification request 1045 (e.g., may comprise new UPF 110 address, newUPF 110 DL tunnel ID, and/or the like). In an example, if the servicerequest may be triggered by the network, and/or the SMF 160 may removethe old (intermediate) UPF 110-2, the SMF 160 may send the N4 sessionmodification request message to the old (intermediate) UPF 110-2, andmay provide the DL tunnel information for the buffered DL data. If theSMF 160 may allocate new I-UPF 110, the DL tunnel information is fromthe new (intermediate) UPF 110 may act as N3 terminating point. If theSMF 160 may not allocate a new I-UPF 110, the DL tunnel information maybe from the new UPF 110 (PSA) 110-3 acting as N3 terminating point. TheSMF 160 may start a timer to monitor the forwarding tunnel. In anexample, the old (intermediate) UPF 110-2 may send N4 sessionmodification response message to the SMF 160.

In an example, if the I-UPF 110-2 may be relocated and forwarding tunnelwas established to the new I-UPF 110, the old (intermediate) UPF 110-2may forward its buffered data to the new (intermediate) UPF 110 actingas N3 terminating point. In an example, if the old I-UPF 110-2 may beremoved and the new I-UPF 110 may not be assigned for the PDU sessionand forwarding tunnel may be established to the UPF 110 (PSA) 110-3, theold (intermediate) UPF 110-2 may forward its buffered data to the UPF110 (PSA) 110-3 acting as N3 terminating point.

In an example, the SMF 160 may send to the AMF 155 an N11 message 1060e.g., a Nsmf_PDUSession_UpdateSMContext response (comprising: N1 SMcontainer (PDU session ID, PDU session re-establishment indication), N2SM information (PDU session ID, QoS profile, CN N3 tunnel info,S-NSSAI), Cause), upon reception of the Nsmf_PDUSession_UpdateSMContextrequest with a cause including e.g., establishment of user planeresources. The SMF 160 may determine whether UPF 110 reallocation may beperformed, based on the UE 100 location information, UPF 110 servicearea and operator policies. In an example, for a PDU session that theSMF 160 may determine to be served by the current UPF 110, e.g., PDUsession anchor or intermediate UPF, the SMF 160 may generate N2 SMinformation and may send an Nsmf_PDUSession_UpdateSMContext response1060 to the AMF 155 to establish the user plane(s). The N2 SMinformation may contain information that the AMF 155 may provide to theRAN 105. In an example, for a PDU session that the SMF 160 may determineas requiring a UPF 110 relocation for PDU session anchor UPF, the SMF160 may reject the activation of UP of the PDU session by sendingNsmf_PDUSession_UpdateSMContext response that may contain N1 SMcontainer to the UE 100 via the AMF 155. The N1 SM container may includethe corresponding PDU session ID and PDU session re-establishmentindication.

Upon reception of the Namf_EventExposure_Notify from the AMF 155 to theSMF 160, with an indication that the UE 100 is reachable, if the SMF 160may have pending DL data, the SMF 160 may invoke theNamf_Communication_N1N2MessageTransfer service operation to the AMF 155to establish the user plane(s) for the PDU sessions. In an example, theSMF 160 may resume sending DL data notifications to the AMF 155 in caseof DL data.

In an example, the SMF 160 may send a message to the AMF 155 to rejectthe activation of UP of the PDU session by including a cause in theNsmf_PDUSession_UpdateSMContext response if the PDU session maycorrespond to a LADN and the UE 100 may be outside the area ofavailability of the LADN, or if the AMF 155 may notify the SMF 160 thatthe UE 100 may be reachable for regulatory prioritized service, and thePDU session to be activated may not for a regulatory prioritizedservice; or if the SMF 160 may decide to perform PSA UPF 110-3relocation for the requested PDU session.

In an example, the AMF 155 may send to the (R)AN 105 an N2 requestmessage 1065 (e.g., N2 SM information received from SMF 160, securitycontext, AMF 155 signaling connection ID, handover restriction list, MMNAS service accept, list of recommended cells/TAs/NG-RAN nodeidentifiers). In an example, the RAN 105 may store the security context,AMF 155 signaling connection Id, QoS information for the QoS flows ofthe PDU sessions that may be activated and N3 tunnel IDs in the UE 100RAN 105 context. In an example, the MM NAS service accept may includePDU session status in the AMF 155. If the activation of UP of a PDUsession may be rejected by the SMF 160, the MM NAS service accept mayinclude the PDU session ID and the reason why the user plane resourcesmay not be activated (e.g. LADN not available). Local PDU sessionrelease during the session request procedure may be indicated to the UE100 via the session Status.

In an example, if there are multiple PDU sessions that may involvemultiple SMF 160 s, the AMF 155 may not wait for responses from all SMF160 s before it may send N2 SM information to the UE 100. The AMF 155may wait for all responses from the SMF 160 s before it may send MM NASservice accept message to the UE 100.

In an example, the AMF 155 may include at least one N2 SM informationfrom the SMF 160 if the procedure may be triggered for PDU session userplane activation. AMF 155 may send additional N2 SM information from SMF160 s in separate N2 message(s) (e.g. N2 tunnel setup request), if thereis any. Alternatively, if multiple SMF 160 s may be involved, the AMF155 may send one N2 request message to (R)AN 105 after all theNsmf_PDUSession_UpdateSMContext response service operations from all theSMF 160 s associated with the UE 100 may be received. In such case, theN2 request message may include the N2 SM information received in one ormore of the Nsmf_PDUSession_UpdateSMContext response and PDU session IDto enable AMF 155 to associate responses to relevant SMF 160.

In an example, if the RAN 105 (e.g., NG RAN) node may provide the listof recommended cells/TAs/NG-RAN node identifiers during the AN releaseprocedure, the AMF 155 may include the information from the list in theN2 request. The RAN 105 may use this information to allocate the RAN 105notification area when the RAN 105 may decide to enable RRC inactivestate for the UE 100.

If the AMF 155 may receive an indication, from the SMF 160 during a PDUsession establishment procedure that the UE 100 may be using a PDUsession related to latency sensitive services, for any of the PDUsessions established for the UE 100 and the AMF 155 has received anindication from the UE 100 that may support the CM-CONNECTED with RRCinactive state, then the AMF 155 may include the UE's RRC inactiveassistance information. In an example, the AMF 155 based on networkconfiguration, may include the UE's RRC inactive assistance information.

In an example, the (R)AN 105 may send to the UE 100 a message to performRRC connection reconfiguration 1070 with the UE 100 depending on the QoSinformation for all the QoS flows of the PDU sessions whose UPconnections may be activated and data radio bearers. In an example, theuser plane security may be established.

In an example, if the N2 request may include a MM NAS service acceptmessage, the RAN 105 may forward the MM NAS service accept to the UE100. The UE 100 may locally delete context of PDU sessions that may notbe available in SGC.

In an example, if the N1 SM information may be transmitted to the UE 100and may indicate that some PDU session(s) may be re-established, the UE100 may initiate PDU session re-establishment for the PDU session(s)that me be re-established after the service request procedure may becomplete.

In an example, after the user plane radio resources may be setup, theuplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105(e.g., NG-RAN) may send the uplink data to the UPF 110 address andtunnel ID provided.

In an example, the (R)AN 105 may send to the AMF 155 an N2 request Ack1105 (e.g., N2 SM information (comprising: AN tunnel info, list ofaccepted QoS flows for the PDU sessions whose UP connections areactivated, list of rejected QoS flows for the PDU sessions whose UPconnections are activated)). In an example, the N2 request message mayinclude N2 SM information(s), e.g. AN tunnel info. RAN 105 may respondN2 SM information with separate N2 message (e.g. N2 tunnel setupresponse). In an example, if multiple N2 SM information are included inthe N2 request message, the N2 request Ack may include multiple N2 SMinformation and information to enable the AMF 155 to associate theresponses to relevant SMF 160.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (ANtunnel info), RAT type) per PDU session. If the AMF 155 may receive N2SM information (one or multiple) from the RAN 105, then the AMF 155 mayforward the N2 SM information to the relevant SMF 160. If the UE 100time zone may change compared to the last reported UE 100 Time Zone thenthe AMF 155 may include the UE 100 time zone IE in theNsmf_PDUSession_UpdateSMContext request message.

In an example, if dynamic PCC is deployed, the SMF 160 may initiatenotification about new location information to the PCF 135 (ifsubscribed) by invoking an event exposure notification operation (e.g.,a Nsmf_EventExposure_Notify service operation). The PCF 135 may provideupdated policies by invoking a policy control update notificationmessage 1115 (e.g., a Npcf_SMPolicyControl_UpdateNotify operation).

In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110 for the PDU session, the SMF 160 may initiates anN4 session modification procedure 1120 to the new I-UPF 110 and mayprovide AN tunnel info. The downlink data from the new I-UPF 110 may beforwarded to RAN 105 and UE 100. In an example, the UPF 110 may send tothe SMF 160, an N4 session modification response 1120. In an example,the SMF 160 may send to the AMF 155, an Nsmf_PDUSession_UpdateSMContextresponse 1140.

In an example, if forwarding tunnel may be established to the new I-UPF110 and if the timer SMF 160 set for forwarding tunnel may be expired,the SMF 160 may sends N4 session modification request 1145 to new(intermediate) UPF 110 acting as N3 terminating point to release theforwarding tunnel. In an example, the new (intermediate) UPF 110 maysend to the SMF 160 an N4 session modification response 1145. In anexample, the SMF 160 may send to the PSA UPF 110-3 an N4 sessionmodification request 1150, or N4 session release request. In an example,if the SMF 160 may continue using the old UPF 110-2, the SMF 160 maysend an N4 session modification request 1155, providing AN tunnel info.In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3,the SMF 160 may initiate resource release, after timer expires, bysending an N4 session release request (release cause) to the oldintermediate UPF 110-2.

In an example, the old intermediate UPF 110-2 may send to the SMF 160 anN4 session modification response or N4 session release response 1155.The old UPF 110-2 may acknowledge with the N4 session modificationresponse or N4 session release response message to confirm themodification or release of resources. The AMF 155 may invoke theNamf_EventExposure_Notify service operation to notify the mobilityrelated events, after this procedure may complete, towards the NFs thatmay have subscribed for the events. In an example, the AMF 155 mayinvoke the Namf_EventExposure_Notify towards the SMF 160 if the SMF 160had subscribed for UE 100 moving into or out of area of interest and ifthe UE's current location may indicate that it may be moving into ormoving outside of the area of interest subscribed, or if the SMF 160 hadsubscribed for LADN DNN and if the UE 100 may be moving into or outsideof an area where the LADN is available, or if the UE 100 may be in MICOmode and the AMF 155 had notified an SMF 160 of the UE 100 beingunreachable and that SMF 160 may not send DL data notifications to theAMF 155, and the AMF 155 may informs the SMF 160 that the UE 100 isreachable, or if the SMF 160 had subscribed for UE 100 reachabilitystatus, then the AMF 155 may notify the UE 100 reachability.

An example PDU session establishment procedure depicted in FIG. 12 andFIG. 13. In an example embodiment, when the PDU session establishmentprocedure may be employed, the UE 100 may send to the AMF 155 a NASMessage 1205 (or a SM NAS message) comprising NSSAI, S-NSSAI (e.g.,requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/or thelike), DNN, PDU session ID, request type, old PDU session ID, N1 SMcontainer (PDU session establishment request), and/or the like. In anexample, the UE 100, in order to establish a new PDU session, maygenerate a new PDU session ID. In an example, when emergency service maybe required and an emergency PDU session may not already be established,the UE 100 may initiate the UE 100 requested PDU session establishmentprocedure with a request type indicating emergency request. In anexample, the UE 100 may initiate the UE 100 requested PDU sessionestablishment procedure by the transmission of the NAS messagecontaining a PDU session establishment request within the N1 SMcontainer. The PDU session establishment request may include a PDU type,SSC mode, protocol configuration options, and/or the like. In anexample, the request type may indicate initial request if the PDUsession establishment is a request to establish the new PDU session andmay indicate existing PDU session if the request refers to an existingPDU session between 3GPP access and non-3GPP access or to an existingPDN connection in EPC. In an example, the request type may indicateemergency request if the PDU session establishment may be a request toestablish a PDU session for emergency services. The request type mayindicate existing emergency PDU session if the request refers to anexisting PDU session for emergency services between 3GPP access andnon-3GPP access. In an example, the NAS message sent by the UE 100 maybe encapsulated by the AN in a N2 message towards the AMF 155 that mayinclude user location information and access technology typeinformation. In an example, the PDU session establishment requestmessage may contain SM PDU DN request container containing informationfor the PDU session authorization by the external DN. In an example, ifthe procedure may be triggered for SSC mode 3 operation, the UE 100 mayinclude the old PDU session ID which may indicate the PDU session ID ofthe on-going PDU session to be released, in the NAS message. The old PDUsession ID may be an optional parameter which may be included in thiscase. In an example, the AMF 155 may receive from the AN the NAS message(e.g., NAS SM message) together with user location information (e.g.cell ID in case of the RAN 105). In an example, the UE 100 may nottrigger a PDU session establishment for a PDU session corresponding to aLADN when the UE 100 is outside the area of availability of the LADN.

In an example, the AMF 155 may determine that the NAS message or the SMNAS message may correspond to the request for the new PDU session basedon that request type indicates initial request and that the PDU sessionID may not be used for any existing PDU session(s) of the UE 100. If theNAS message does not contain an S-NSSAI, the AMF 155 may determine adefault S-NSSAI for the requested PDU session either according to the UE100 subscription, if it may contain only one default S-NSSAI, or basedon operator policy. In an example, the AMF 155 may perform SMF 160selection 1210 and select an SMF 160. If the request type may indicateinitial request or the request may be due to handover from EPS, the AMF155 may store an association of the S-NSSAI, the PDU session ID and aSMF 160 ID. In an example, if the request type is initial request and ifthe old PDU session ID indicating the existing PDU session may becontained in the message, the AMF 155 may select the SMF 160 and maystore an association of the new PDU session ID and the selected SMF 160ID.

In an example, the AMF 155 may send to the SMF 160, an N11 message 1215,e.g., Nsmf_PDUSession_CreateSMContext request (comprising: SUPI or PEI,DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container(PDU session establishment request), user location information, accesstype, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN,S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDUsession establishment request), user location information, access type,RAT type, PEI). In an example, if the AMF 155 may not have anassociation with the SMF 160 for the PDU session ID provided by the UE100 (e.g when request type indicates initial request), the AMF 155 mayinvoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155already has an association with an SMF 160 for the PDU session IDprovided by the UE 100 (e.g when request type indicates existing PDUsession), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContextrequest. In an example, the AMF 155 ID may be the UE's GUAMI whichuniquely identifies the AMF 155 serving the UE 100. The AMF 155 mayforward the PDU session ID together with the N1 SM container containingthe PDU session establishment request received from the UE 100. The AMF155 may provide the PEI instead of the SUPI when the UE 100 hasregistered for emergency services without providing the SUPI. In casethe UE 100 has registered for emergency services but has not beenauthenticated, the AMF 155 may indicate that the SUPI has not beenauthenticated.

In an example, if the request type may indicate neither emergencyrequest nor existing emergency PDU session and, if the SMF 160 has notyet registered and subscription data may not be available, the SMF 160may register with the UDM 140, and may retrieve subscription data 1225and subscribes to be notified when subscription data may be modified. Inan example, if the request type may indicate existing PDU session orexisting emergency PDU session, the SMF 160 may determine that therequest may be due to handover between 3GPP access and non-3GPP accessor due to handover from EPS. The SMF 160 may identify the existing PDUsession based on the PDU session ID. The SMF 160 may not create a new SMcontext but instead may update the existing SM context and may providethe representation of the updated SM context to the AMF 155 in theresponse. if the request type may be initial request and if the old PDUsession ID may be included in Nsmf_PDUSession_CreateSMContext request,the SMF 160 may identify the existing PDU session to be released basedon the old PDU session ID.

In an example, the SMF 160 may send to the AMF 155, the N11 messageresponse 1220, e.g., either a PDU session create/update response,Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID orN1 SM container (PDU session reject(cause))) or anNsmf_PDUSession_UpdateSMContext response.

In an example, if the SMF 160 may perform secondaryauthorization/authentication 1230 during the establishment of the PDUsession by a DN-AAA server, the SMF 160 may select a UPF 110 and maytrigger a PDU session establishment authentication/authorization.

In an example, if the request type may indicate initial request, the SMF160 may select an SSC mode for the PDU session. The SMF 160 may selectone or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF160 may allocate an IP address/prefix for the PDU session. In case ofPDU type IPv6, the SMF 160 may allocate an interface identifier to theUE 100 for the UE 100 to build its link-local address. For UnstructuredPDU type the SMF 160 may allocate an IPv6 prefix for the PDU session andN6 point-to-point tunneling (based on UDP/IPv6).

In an example, if dynamic PCC is deployed, the may SMF 160 performs PCF135 selection 1235. If the request type indicates existing PDU sessionor existing emergency PDU session, the SMF 160 may use the PCF 135already selected for the PDU session. If dynamic PCC is not deployed,the SMF 160 may apply local policy.

In an example, the SMF 160 may perform a session management policyestablishment procedure 1240 to establish a PDU session with the PCF 135and may get the default PCC Rules for the PDU session. The GPSI may beincluded if available at the SMF 160. If the request type in 1215indicates existing PDU session, the SMF 160 may notify an eventpreviously subscribed by the PCF 135 by a session management policymodification procedure and the PCF 135 may update policy information inthe SMF 160. The PCF 135 may provide authorized session-AMBR and theauthorized 5QI and ARP to SMF 160. The PCF 135 may subscribe to the IPallocation/release event in the SMF 160 (and may subscribe otherevents).

In an example, the PCF 135, based on the emergency DNN, may set the ARPof the PCC rules to a value that may be reserved for emergency services.

In an example, if the request type in 1215 indicates initial request,the SMF 160 may select an SSC mode for the PDU session. The SMF 160 mayselect 1245 one or more UPFs as needed. In case of PDU type IPv4 orIPv6, the SMF 160 may allocate an IP address/prefix for the PDU session.In case of PDU type IPv6, the SMF 160 may allocate an interfaceidentifier to the UE 100 for the UE 100 to build its link-local address.For unstructured PDU type the SMF 160 may allocate an IPv6 prefix forthe PDU session and N6 point-to-point tunneling (e.g., based onUDP/IPv6). In an example, for Ethernet PDU type PDU session, neither aMAC nor an IP address may be allocated by the SMF 160 to the UE 100 forthis PDU session.

In an example, if the request type in 1215 is existing PDU session, theSMF 160 may maintain the same IP address/prefix that may be allocated tothe UE 100 in the source network.

In an example, if the request type in 1215 indicates existing PDUsession referring to an existing PDU session moved between 3GPP accessand non-3GPP access, the SMF 160 may maintain the SSC mode of the PDUsession, e.g., the current PDU session Anchor and IP address. In anexample, the SMF 160 may trigger e.g. new intermediate UPF 110 insertionor allocation of a new UPF 110. In an example, if the request typeindicates emergency request, the SMF 160 may select 1245 the UPF 110 andmay select SSC mode 1.

In an example, the SMF 160 may perform a session management policymodification 1250 procedure to report some event to the PCF 135 that haspreviously subscribed. If request type is initial request and dynamicPCC is deployed and PDU type is IPv4 or IPv6, the SMF 160 may notify thePCF 135 (that has previously subscribed) with the allocated UE 100 IPaddress/prefix.

In an example, the PCF 135 may provide updated policies to the SMF 160.The PCF 135 may provide authorized session-AMBR and the authorized 5QIand ARP to the SMF 160.

In an example, if request type indicates initial request, the SMF 160may initiate an N4 session establishment procedure 1255 with theselected UPF 110. The SMF 160 may initiate an N4 session modificationprocedure with the selected UPF 110. In an example, the SMF 160 may sendan N4 session establishment/modification request 1255 to the UPF 110 andmay provide packet detection, enforcement, reporting rules, and/or thelike to be installed on the UPF 110 for this PDU session. If CN tunnelinfo is allocated by the SMF 160, the CN tunnel info may be provided tothe UPF 110. If the selective user plane deactivation is required forthis PDU session, the SMF 160 may determine the Inactivity Timer and mayprovide it to the UPF 110. In an example, the UPF 110 may acknowledgesby sending an N4 session establishment/modification response 1255. If CNtunnel info is allocated by the UPF, the CN tunnel info may be providedto SMF 160. In an example, if multiple UPFs are selected for the PDUsession, the SMF 160 may initiate N4 session establishment/modificationprocedure 1255 with one or more UPF 110 of the PDU session.

In an example, the SMF 160 may send to the AMF 155 anNamf_Communication_N1N2MessageTransfer 1305 message (comprising PDUsession ID, access type, N2 SM information (PDU session ID, QFI(s), QoSprofile(s), CN tunnel info, S-NSSAI, session-AMBR, PDU session type,and/or the like), N1 SM container (PDU session establishment accept (QoSRule(s), selected SSC mode, S-NSSAI, allocated IPv4 address, interfaceidentifier, session-AMBR, selected PDU session type, and/or the like))).In case of multiple UPFs are used for the PDU session, the CN tunnelinfo may comprise tunnel information related with the UPF 110 thatterminates N3. In an example, the N2 SM information may carryinformation that the AMF 155 may forward to the (R)AN 105 (e.g., the CNtunnel info corresponding to the core network address of the N3 tunnelcorresponding to the PDU session, one or multiple QoS profiles and thecorresponding QFIs may be provided to the (R)AN 105, the PDU session IDmay be used by AN signaling with the UE 100 to indicate to the UE 100the association between AN resources and a PDU session for the UE100,and/or the like). In an example, a PDU session may be associated to anS-NSSAI and a DNN. In an example, the N1 SM container may contain thePDU session establishment accept that the AMF 155 may provide to the UE100. In an example, multiple QoS rules and QoS profiles may be includedin the PDU session establishment accept within the N1 SM and in the N2SM information. In an example, theNamf_Communication_N1N2MessageTransfer 1305 may further comprise the PDUsession ID and information allowing the AMF 155 to know which accesstowards the UE 100 to use.

In an example, the AMF 155 may send to the (R)AN105 an N2 PDU sessionrequest 1310 (comprising N2 SM information, NAS message (PDU session ID,N1 SM container (PDU session establishment accept, and/or the like))).In an example, the AMF 155 may send the NAS message 1310 that maycomprise PDU session ID and PDU session establishment accept targeted tothe UE 100 and the N2 SM information received from the SMF 160 withinthe N2 PDU session request 1310 to the (R)AN 105.

In an example, the (R)AN 105 may issue AN specific signaling exchange1315 with the UE 100 that may be related with the information receivedfrom SMF 160. In an example, in case of a 3GPP RAN 105, an RRCconnection reconfiguration procedure may take place with the UE 100 toestablish the RAN 105 resources related to the QoS Rules for the PDUsession request 1310. In an example, (R)AN 105 may allocate (R)AN 105 N3tunnel information for the PDU session. In case of dual connectivity,the master RAN 105 node may assign some (zero or more) QFIs to be setupto a master RAN 105 node and others to the secondary RAN 105 node. TheAN tunnel info may comprise a tunnel endpoint for one or more involvedRAN 105 nodes, and the QFIs assigned to one or more tunnel endpoints. AQFI may be assigned to either the master RAN 105 node or the secondaryRAN 105 node. In an example, (R)AN 105 may forward the NAS message 1310(PDU session ID, N1 SM container (PDU session establishment accept)) tothe UE 100. The (R)AN 105 may provide the NAS message to the UE 100 ifthe RAN 105 resources are established and the allocation of (R)AN 105tunnel information are successful.

In an example, the N2 PDU session response 1320 may comprise a PDUsession ID, cause, N2 SM information (PDU session ID, AN tunnel info,list of accepted/rejected QFI(s)), and/or the like. In an example, theAN tunnel info may correspond to the access network address of the N3tunnel corresponding to the PDU session.

In an example, the AMF 155 may forward the N2 SM information receivedfrom (R)AN 105 to the SMF 160 via a Nsmf_PDUSession_UpdateSMContextrequest 1330 (comprising: N2 SM information, request type, and/or thelike). In an example, if the list of rejected QFI(s) is included in N2SM information, the SMF 160 may release the rejected QFI(s) associatedQoS profiles.

In an example, the SMF 160 may initiate an N4 session modificationprocedure 1335 with the UPF110. The SMF 160 may provide AN tunnel infoto the UPF 110 as well as the corresponding forwarding rules. In anexample, the UPF 110 may provide an N4 session modification response1335 to the SMF 160160.

In an example, the SMF 160 may send to the AMF 155 anNsmf_PDUSession_UpdateSMContext response 1340 (Cause). In an example,the SMF 160 may subscribe to the UE 100 mobility event notification fromthe AMF 155 (e.g. location reporting, UE 100 moving into or out of areaof interest), after this step by invoking Namf_EventExposure_Subscribeservice operation. For LADN, the SMF 160 may subscribe to the UE 100moving into or out of LADN service area event notification by providingthe LADN DNN as an indicator for the area of interest. The AMF 155 mayforward relevant events subscribed by the SMF 160.

In an example, the SMF 160 may send to the AMF 155, aNsmf_PDUSession_SMContextStatusNotify (release) 1345. In an example, ifduring the procedure, any time the PDU session establishment is notsuccessful, the SMF 160 may inform the AMF 155 by invoking NsmfPDUSession_SMContextStatusNotify(release) 1345. The SMF 160 may releasesany N4 session(s) created, any PDU session address if allocated (e.g IPaddress) and may release the association with the PCF 135.

In an example, in case of PDU type IPv6, the SMF 160 may generate anIPv6 Router Advertisement 1350 and may send it to the UE 100 via N4 andthe UPF 110.

In an example, if the PDU session may not be established, the SMF 160may unsubscribe 1360 to the modifications of session managementsubscription data for the corresponding (SUPI, DNN, S-NSSAI), usingNudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI), if the SMF 160 is no morehandling a PDU session of the UE 100 for this (DNN, S-NSSAI). In anexample, if the PDU session may not be established, the SMF 160 mayderegister 1360 for the given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID).

The 5GS may be operated as stand-alone time sensitive networking (TSN)network or part of a non-stand-alone TSN network, e.g. an industrialcommunication network, and/or the like. 5GS may support three modes ofoperation as depicted in example FIG. 15. In a fully distributed modelshown at the bottom of FIG. 15, the TSN end stations, e.g., talkers andlisteners, may communicate TSN stream requirements directly to the TSNnetwork. Each TSN bridge on the path from talker to listeners maypropagate the TSN user and network configuration information along withthe active topology for the TSN stream to the neighboring bridge(s). Thenetwork resources may be managed locally in each TSN bridge. In acentralized network and distributed user model shown in the middle ofFIG. 15, the TSN end stations, e.g., Talkers and Listeners, maycommunicate the TSN stream requirements directly to the TSN network. TheTSN stream requirements are forwarded to a centralized networkconfiguration (CNC). The TSN bridges may provide their networkcapabilities information and active topology information to the CNC. TheCNC may have a complete view of the TSN network and is enabled tocompute respective end-to-end communication paths from a talker to thelisteners that fulfil the TSN stream requirements as provided by the endstations. The computation result may be provided by the CNC as TSNconfiguration information to each TSN bridge in the path betweeninvolved TSN end stations (Talkers to the Listeners) as networkconfiguration information. In a fully centralized model shown at the topof FIG. 15, the TSN end stations, e.g., Talkers and Listeners, maycommunicate the TSN stream requirements to a centralized userconfiguration (CUC). The CUC may adapt the TSN end station streamrequirements before forwarding them to the CNC. The CNC performs thesame actions as described in the centralized network/distributed usermodel, except that CNC may send specific TSN configuration informationto the CUC. The CUC may determine/derive the TSN configurationinformation for the TSN end stations and notify them accordingly.

In an example, a TSN system may employ 5GS as a TSN link, as a TSNbridge, and/or the like. The TSN system may be integrated with a 5GS.

As depicted in example FIG. 17, the 5GS may be employed to the externalnetwork as a TSN link, e.g., as an Ethernet connection/link between a UEand a UPF. The link may be defined by the connected entities, i.e.either two TSN bridges or a TSN end station and a TSN bridge, two TSNend stations, and/or the like. The link capabilities may be described bythe ingress/egress ports of the TSN bridges connected to the end of alink or by the TSN streaming requirements of a TSN end station directlyconnected to the link. The exposed capabilities may comprise delayinformation, link speed, available bandwidth information, and/or thelike.

In an example as depicted in FIG. 18 and FIG. 19, 5GS may be employed asa TSN bridge. The 5GD may receive TSN related reservation requests usinga 5G QoS framework. The 5GS may employ 5G internal signaling to satisfyTSN reservation requests. When the 5GS is deployed as a TSN bridge(e.g., logical TSN bridge), the TSN bridge may comprise an adaptationfunction to translate the 5GS protocols and information objects to TSNprotocols and information objects and vice versa. The 5GS bridge mayprovide TSN ingress and egress ports via a TSN Translator (Device) onthe UE side and via the “TSN Translator” (CP and UP) on the CN sidetowards the DN. The 5GS bridge may support different TSN configurationmodels. In an example, one or more TSN compliant interfaces may beemployed by the TSN bridge with the respective protocols towards TSN endstations, TSN bridges, CNC, CUC, and/or the like on the control planeand/or user plane. The TSN bridge self-management and the functionsrequired to interact with CNC may be located at the network translator.

In an example, as depicted in FIG. 20, a 5GS may be integrated with aTSN system. When the 5GS is integrated with the TSN system, individualnodes of the 5GS (e.g. UPF, gNB, and/or the like) may interact with TSNprocedures initiated by TSN end-points and TSN controllers. This allowsthe 5GS and associated infrastructure to present itself as multipleTSN-compatible end-points.

As depicted in an example FIG. 14, 5GS may be integrated with a TSNsystem. The TSN system may generate control and data traffic and send tothe 5GS. Control and data traffic may comprise TSN QoS information,stream information, port information, and/or the like. Ethernet framesand/or headers may be mapped to or encapsulated within 5G frames/packetsand sent via an air interface to the 5GS. A 5G radio with an integratedEthernet adapter may be connected to a wireless device (UE).

In an example embodiment, a 3GPP network may support derivation of TSNbridge delay managed object attributes (e.g., independentDelayMin/Max,dependentDelayMin/Max, and/or the like) for a 3GPP bridge based on 3GPPattributes, e.g., QoS flow packet delay budget (PDB) values, guaranteedflow bit rate (GFBR), the maximum data burst volume (MDBV) indicated inthe QoS profile, and/or the like. Mapping of 3GPP attributes to TSNcapabilities may be in the SMF and/or PCF and the exposure ofcapabilities towards TSN bridge may be via NEF, SMF, PCF, and/or thelike.

In an example, a TSN bridge delay managed object may comprise framelength-related attributes per tuple (ingress port, egress port, trafficclass). Frame length-related attributes may comprise: independentDelayMin/Max (e.g., incurred bridge delay independent of the frame size(typically in ns)), dependentDelay Min/Max (e.g., incurred bridge delayper base volume (typically in ps per byte)), and/or the like.

In an example as depicted in FIG. 21, when centralized model or thefully centralized model and the centralized network/distributed usermodel is employed in TSN network, the 5GS may be enhanced to act as aTSN bridge in the network. An AF may act as a controller function tocollect 5GS virtual bridge related information and register it to CNCvia TSN defined application interfaces, since the CNC maintainscapabilities of each TSN bridge in the TSN network and the topology ofthe network. In an example, based on the information that the CNCmaintains, the CNC may calculate the forwarding and scheduling rules oneach bridge for a TSN stream that required by CUC which collects the TSNstream requirements from end stations for fully centralized model. In anexample, a control plane based QoS negotiation may be employed. Asdepicted in FIG. 21, the CNC may negotiate with a PCF through the TSN AFto generate a TSN-aware QoS profile for a stream. The TSN AF may convertTSN traffic characteristics to TSN QoS requirements, TSN QoS Profile,and/or the like.

In an example, for the control plane based solution, the AF may act as acontroller function to collect 5GS virtual bridge related information(e.g. AF receives the information from SMF and may register it to CNCvia TSN defined application interfaces). The information may comprise:bridge identity, port identities, bridge delay, sending delay, bridgerelated topology information, and/or the like. In an example, bridgeidentity may identify a TSN bridge in the TSN network. In an example,ports identities may identify ports in a TSN bridge. Bridge delay maycomprise a delay value of frames as they pass through the bridge, thatmay comprise maximum and minimum of independent and dependent delay.Sending delay may be the delay for a frame transmitted from a TSN bridgeport to a neighboring port on a different bridge. Bridge relatedtopology may comprise the bridge and port identities and portcapabilities of a TSN bridge and neighboring bridges. In an example,identities of the virtual bridge and related ports of the UPF may bepreconfigured on the UPF and may be reported to the AF via the SMF whenthe UPF sets up. The UE or PDU session may be virtualized to be avirtual port on the virtual bridge with a (unique) identity that may beallocated by the SMF or the UPF. The TSN AF may interact with the 5G CNand may perform the mapping between TSN network parameters and a newdeterministic QoS profile for the 5GS, negotiate the traffic treatmentand related QoS policies, and/or the like. In an example, the TSN AF maydirectly talk to the other 5GC NFs or via the NEF.

In an example, 5GS virtual bridge information may comprise bridge ID,port IDs, bridge internal information (e.g., bridge delay) and bridgeport related information (e.g., propagation delay), and/or the like.Information for 5GS virtual bridge may be reported to AF by 5GS controlplane, like the bridge ID, port IDs, bridge internal information (e.g.,bridge delay) and bridge port related information (e.g., propagationdelay), and/or the like.

In an example as depicted in FIG. 42, the 5GS virtual bridge may be perUPF, per TSN network (indicated by DNN), and the 5GS virtual bridge userplane may comprise UPF ports and the UE ports connected to such UPFports via PDU session. Identities of the virtual bridge and related UPFports may be preconfigured on UPF and may be reported to AF through SMFwhen UPF sets up or the PDU Session is established. The UE port identitymay be unique in a 5GS virtual bridge and the UE port identity may beallocated by UPF. The UPF port and UE port related information may bereported to AF by SMF directly or via NEF. The UPF port relatedinformation may be reported to the SMF by UPF using the node levelsignaling or PDU session level signaling. The UE port relatedinformation may be reported by UE to the SMF over NAS or over UP of itscorresponding PDU session. In an example, a UE may operate in switchmode, Ethernet switch mode, and/or the like. In an example, the UE portof 5GS virtual bridge may be the physical port of UE, virtualport/interface of the UE, and/or the like.

In an example, traffic scheduling in TSN bridge may be per trafficclass, which is service level of packets transmission. A TSN bridge portmay support different traffic classes. In an example, if the TSN bridgeis aware of VLAN, a TSN bridge port may support different VLANs. WhenSMF selects the UPF for the PDU Session, it may consider the UEsubscribed traffic classes and VLANs.

As depicted in example FIG. 42, UPF1 and UPF2 support different VLANsand traffic classes based on deployment. When UE1 and UE2 establish PDUsession, the UPF1 and UPF2 are selected respectively to meet theirsubscribed VLANs and traffic classes. As the bridge delay defined in802.1QCC is per traffic class per port pair, the UPF may determine theright port pairs to serve the PDU session, and the SMF may report bridgedelay on such port pairs. For UE1 in the figure for example, the UPF1may determine the Port1, which supports traffic class 2, VLAN 100requested by UE1, to serve the PDU Session. Then SMF may report thebridge delay of traffic class 2 for port pair (UE1 port and UPF1 Portl).

In an example as depicted in FIG. 43, for 5GS virtual bridge topologydiscovery, the UPF and UE may report topology information as 802.1ABdefined to SMF when received link layer discovery protocol (LLDP)packets from one or more devices (e.g., UE, end station, TSN device,Ethernet device, and/or the like). The topology information may bereported when it is discovered at the first time or when it ischanged/modified. The UPF and UE may send LLDP packets in order toenable the one or more devices discovering/reporting the 5GS virtualbridge. One or more port of 5GS virtual bridge may support sending LLDPor receiving LLDP. For propagation delay and port capabilities as802.1Qcc defined, the UPF and UE may report them to SMF similar astopology information reporting. The 5GS may support TSN network specificQoS characteristics and the mapping between such QoS characteristics andthe traffic classes. Packet delay budget (PDB) in the QoScharacteristics may be employed to realize the maximum latencytransmission for deterministic delivery. The SMF may get the QoScharacteristics for UE's subscribed traffic classes and SMF may employthe PDB in them as the bridge delay for the corresponding traffic classon the port pair. The AF may collect/gather/obtain/receive and maymaintain 5GS virtual bridge related information. The AF may act as thecontrol plane of the 5GS virtual bridge, and may register or updatethose information to CNC as 802.1Qcc and 802.1AB defined. For QoSprofile generation, the AF may maintain the relationship between UE ID,5GS virtual bridge ID and UE port ID. The AF may determine/find thecorresponding UE ID when receiving TSN stream rule (Bridge ID, Ingressport ID, Egress port ID, Stream description, stream id, and/or the like)from CNC. The AF may determine the traffic class in the TSN stream ruleand map the traffic class to corresponding 5QI.

In an example embodiment, a TSN bridge may report capabilities. In anexample, identities of 5GS virtual bridge and UPF ports may bepre-configured on UPF based on deployment. The UPF may report its portcapabilities and propagation delay as 802.1Qcc defined, the topologyinformation as 802.1AB defined, and the corresponding DNN to SMF usingnode level singling, and the SMF may forward the received information tothe AF directly or via NEF in order to generate or update the 5GSvirtual bridge and bridge port. The UE may send PDU sessionestablishment request to the AMF. The AMF may select a SMF for the PDUSession. The SMF may receive the UE subscribed traffic classes and VLANsfrom the UDM, and may receive the QoS characteristics (e.g., 5QI, PDB)corresponding to the subscribed traffic classes from PCF. The SMF mayselect a UPF to support the subscribed traffic classes and subscribedVLANs. The SMF may send N4 session establishment request to UPF withDNN, traffic class IDs and VLAN values to request for allocating UE portID and determining serving UPF ports. The UPF may determine the 5GSvirtual bridge for the PDU session, and may allocate an identity for UEport. Based on the traffic classes and VLANs that UPF port supports inthe DN, the UPF may determine the UPF ports to serve the PDU session.The UPF may send the allocated UE port identity with corresponding 5GSvirtual bridge identity, the serving UPF port IDs with correspondingtraffic class IDs, and/or the like to the SMF. The SMF may send the PDUsession related 5GS virtual bridge ID and may allocate UE port ID to UE.The information may be employed for UE to perform topology discovery andinformation reporting. The SMF may take the PDB in QoS characteristicsas the bridge delay for corresponding traffic class and port pair, andmay send the 5GS virtual bridge related information (bridge delay, UEport ID, UPF port ID, traffic class, 5GS virtual bridge ID, UE ID) tothe AF or via NEF in order to add the UE port or update the bridgeproperties.

In an example, when the PDU session is established, the UE may reportits port capabilities and propagation delay as 802.1Qcc defined andreport the topology information as 802.1AB defined to SMF over NAS oruser plane. The AF may receive/collect/gather and may maintain the 5GSvirtual bridge properties including bridge ID, port ID of UPF ports,port ID of UE ports, port related capabilities and bridge delay of portpairs, and/or the like. The AF may send the 5GS virtual bridgeproperties to CNC to create a TSN bridge or update the bridge when thebridge properties are changed.

In an example embodiment, the UE may operate as an Ethernet switch. TheSMF may configure the UE to operate as an Ethernet switch withconfiguration parameters provided during the establishment of a PDUSession, or configuration of the TSN bridge. The PDU session may provideaccess to the end station via the TSN bridge to communication with oneor more end stations. The UE operating as an Ethernet switch may be partof one or more TSN systems. One or more backend devices may be connectedto the UE operating as an Ethernet switch. In an example, the SMF mayprovide configuration parameters to the UE in switch mode. Theconfiguration parameters may comprise an indicator whether the UE inEthernet switch mode may turn on or off the Spanning Tree Algorithm, aperiodic timer of sending BDPU messages, a bridge identifier of the UEin Ethernet switch mode, an indicator whether the UE in Ethernet switchmode may notify the change of port's status, an indicator whether the UEin Ethernet switch mode may report the list of MAC address(es) of theTSN end stations, backend devices, and/or the like connected in thebackend networks.

In an example, if the SMF indicates to the UE to report the list of MACaddress(es) of the backend devices or the TSN end stations, the UE inswitch mode may obtain the list of MAC address(es) of the backenddevices connected or changed in the backend networks. In an example,when one PDU session provides communication for more than one TSNsystems, the UE may obtain/determine the mapping relationship of MACaddress(es) and the TSN systems. The UE may inform the SMF of the listof MAC address(es) and the mapping relationship during the PDU sessionestablishment/modification procedure when the UE receives the indicatoror detects the changes on the backend devices. The SMF may provide tothe UPF Ethernet packet filter set and forwarding rule(s) based on theMAC address(es) and the mapping relationship. The UPF may detect andforward Ethernet frames based on the Ethernet packet filter set andforwarding rule(s) received from the SMF.

In an example, the UE in Ethernet switch mode may report its port statesthat may result from the execution of the spanning tree algorithm,and/or the like so that the SMF may control the UPF's port states basedon the report to prevent the waste of network resources.

In an example, the UPF may support S-tag (IEEE 802.1ad), C-tag (IEEE802.1q). In an example, a PDU session may provide access to one or moreTSN systems, TSN end station, and/or the like. S-tag and/or C-tag forthe stream of data packets may be employed. TSN system configurationsmay be pre-configured on the UE or provided to the UE by the networke.g., SMF, and/or the like. In an example, a TSN system identifier maybe employed to identify the TSN system, one or more TSN end stations,and/or the like. In an example, the operator may assign the list of TSNsystems or TSN end station identifiers for the UEs. The identifiers maybe configured in the UDR, UDM, and/or the like. The SMF may beconfigured by the operator to have the mapping tables for TSNidentifiers, VLAN ID, C-tag, S-tag, and/or the like. The SMF may map thelist of the TSN end station identifiers connected to the UE, which isnotified through the procedures of PDU Session establishment, into theS-tag and C-tag, and packet filter for the uplink traffic. The UPF mayinsert S-tag and C-tag onto the traffic which is sent to N6, and/or thelike based on the packet filter for the uplink traffic.

In an example, a 3GPP system, 5GS, and/or the like may be employed toact as a TSN bridge. The TSN bridge ports may be deployed at a UE and aUPF. A TSN system may transmit and receive data packets, a stream ofdata packets, and/or the like. In existing technologies, when the UEreceives a request from a TSN station (e.g., a bridge, a switch port, aTSN end station, and/or the like), or from an application related to theTSN system on the UE, the UE may request configuration of a session forthe TSN system or select the route for the request. The UE may select aroute or establish PDU sessions which do not meet the TSN systemrequirements or application preferences and, as a result, applicationsmay not work as expected. Embodiments of the present disclosure providemechanisms to enhance the performance of TSN systems, TSN bridgeconfiguration, and/or the like. Embodiments of the present disclosureprovide implementations of signaling between the UE and 3GPP system thatsupports TSN, configuration of parameters, and signaling for UEconfiguration update (UCU) procedure.

In an example embodiment as depicted in FIG. 22, a TSN AF may beemployed for the conversion/mapping/association between TSN bridgerequirements, TSN traffic characteristics, and/or the like to TSN QoSrequirements, TSN QoS Profile, and/or the like. The TSN AF may provideTSN QoS profile to a PCF (e.g., directly or via NEF). The PCF mayperform a feasibility check with SMF, UDM/UDR, and/or the like, and theSMF may check further with a RAN node, a UPF, and/or the like. If acommunication network/system (e.g., EPC, 5GS, and/or the like) is ableto fulfil the requested QoS profile from the TSN AF, the PCF mayindicate to the acceptance of the requested TSN QoS requirements to theTSN AF. If the 5GS is unable to fulfil the QoS profile requirements, itmay send a reject message to the TSN AF that may be relayed to the CNC,CUC, the TSN system, and/or the like. Based on the agreed QoS profilebetween TSN and the communication network (5G network), the PCF maydetermine one or more related QoS policies and rules and provide that tothe SMF and UE.

In an example embodiment, the PCF may determine/configure a UE routeselection policy (URSP). The URSP may be for a TSN system configurationat the UE. The PCF may generate the URSP with a set of one ore morerules/policies that are associated with a traffic descriptor, connectioncapabilities descriptor, and/or the like. In an example, the trafficdescriptor may further comprise a system descriptor. The descriptor maybe a TSN bridge identifier, a TSN port identifier of the UE, a TSN portpriority of the UE, an identifier of the stream (e.g., TSN stream orstream ID) and/or the like. The connection capabilities may be part ofthe traffic descriptor of the URSP. For the URSP rule/policy associatedwith the TSN system, the connection capabilities indicator may be TSN,TSN bridge, IEEE 802.1Q, and/or the like.

The URSP may be employed by the UE to determine how to route outgoingtraffic. Traffic may be routed to an established PDU session, may beoffloaded to non-3GPP access outside a PDU session, or may triggerestablishment of a new PDU Session, and/or the like. In an example, theURSP may be employed by the UE to determine if a detected applicationmay be associated to an established PDU session, may be offloaded tonon-3GPP access outside a PDU Session, or may trigger the establishmentof a new PDU session. The URSP rules may comprise one or more trafficdescriptors that specify the matching criteria and one or more of thefollowing components: SSC mode selection policy (SSCMSP) that may beemployed by the UE to associate the matching application with SSC modes,a network slice selection policy (NSSP) that may be employed by the UEto associate the matching application with S-NSSAI, a DNN selectionpolicy that may be employed by the UE to associate the matchingapplication with the DNN, a PDU session type policy that may be employedby the UE to associate the matching application with a PDU session type,a Non-seamless Offload Policy that may be employed by the UE todetermine that the matching application may be non-seamlessly offloadedto non-3GPP access (e.g., outside of a PDU Session), an access typepreference (e.g., If the UE needs to establish a PDU Session for thematching application, this indicates the preferred access type (3GPP ornon-3GPP)), and/or the like.

In an example, an ANDSP and URSP may be pre-configured in the UE or maybe provisioned to the UE from the PCF. The pre-configured policy may beapplied by the UE when it has not received the same type of policy fromthe PCF. The PCF may select the ANDSP and URSP applicable for one ormore UEs based on local configuration, subscribed S-NSSAIs and operatorpolicies taking into consideration e.g. accumulated usage, load levelinformation per network slice instance, UE location. In the case of aroaming UE, the V-PCF may retrieve ANDSP and URSP from the H-PCF overN24, Npcf, and/or the like. When the UE is roaming and the UE has validrules from both HPLMN and VPLMN, the UE may give priority to the validANDSP rules from the VPLMN. The ANDSP and URSP may be provided from thePCF to the AMF via N15, Namf interface, and/or the like and then fromAMF to the UE via the N1 interface, NAS message, and/or the like. ThePCF may be notified that the UE Policy delivery has failed. When thefailure happens (e.g. because of UE unreachable), the PCF may subscribethe connectivity state changes (IDLE or CONNECTED) event. Afterreception of the notify message indicating that the UE enters theCM-Connected state, the PCF may retry to deliver the UE policy (e.g.,URSP). In an example, when the UE has valid URSP rules, the UE mayperform the association based on user preference and rules. When thereis applicable user preference for the matching application, the userpreference takes precedence over any present route selection component.In an example, the SSC mode selection and network slice selectioncomponents may be prioritized. For the existing PDU session(s), the UEmay examine the URSP rules within the UE policy in order to determinewhether the existing PDU session(s) are maintained. The UE may initiatea PDU Session release procedure for the PDU session(s) that cannot bemaintained.

The URSP, as depicted in example FIG. 32, FIG. 33, FIG. 34, FIG. 35,FIG. 36, FIG. 37, FIG. 38, FIG. 39, FIG. 40, and FIG. 41, may compriseone or more rules for selection of a route based on a trafficdescriptor, a set of one or more traffic descriptors, a list of routeselection descriptors, one or more route selection components, and/orthe like.

In an example as depicted in FIG. 24, when the PCF determines/decides toupdate UE policy, the UE may employ a UE configuration update (UCU)procedure, a UE policy delivery procedure, and/or the like. Theprocedures may be based on triggering conditions such as an initialregistration or a procedure that requires updating UE policy. In anexample, for an initial registration case, the PCF may compare the listof public service identifiers (PSIs) included in the UE access selectionand PDU session selection related policy information inNpcf_UEPolicyControl_Create request and may determine whether UE accessselection and PDU session selection related policy information have tobe updated and be included in the response to the AMF. For the networktriggered UE policy update case (e.g. change of TSN relatedpolicy/configuration, creation of new TSN related configuration policy,change of UE location, the change of subscribed S-NSSAIs, and/or thelike), the PCF may check the latest list of PSIs to decide which UEaccess selection and/or PDU session selection related policies have tobe sent to the UE. The PCF may examine/check if the size of theresulting UE access selection and PDU session selection related policyinformation exceeds a predefined limit. If the size is under the limit,then UE access selection and PDU Session selection related policyinformation may be included in a singleNamf_Communication_N1N2MessageTransfer service operation. If the sizeexceeds the predefined limit, the PCF may split the UE access selectionand PDU session selection related policy information in smaller,logically independent UE access selection and PDU session selectionrelated policy information, ensuring the size of each is under thepredefined limit. One or more URSP, UE access selection, and PDU sessionselection related policy information may be sent in separatedNamf_Communication_N1N2MessageTransfer service operations.

In an example, the PCF may invoke Namf Communication_N1N2MessageTransferservice operation provided by the AMF. The message may comprise SUPI, UEPolicy Container, URSP, and/or the like. If the UE is registered andreachable by AMF in either 3GPP access or non-3GPP access, the AMF maytransfer/send/transmit the UE Policy container to the UE via theregistered and reachable access. If the UE is registered in both 3GPPand non-3GPP accesses and reachable on both access and served by thesame AMF, the AMF may transfer/send/transmit the UE Policy container tothe UE via one of the accesses based on the AMF local policy. If the UEis not reachable by AMF over both 3GPP access and non-3GPP access, theAMF may report to the PCF that the UE policy container may not bedelivered to the UE usingNamf_Communication_N1N2TransferFailureNotification. If the AMFdecides/determines to transfer the UE policy container to the UE via3GPP access, e.g. the UE is registered and reachable by the AMF in 3GPPaccess, or if the UE is registered and reachable by AMF in both 3GPP andnon-3GPP accesses served by the same AMF and the AMF decides to transferthe UE policy container to the UE via 3GPP access based on local policy,and the UE is in CM-IDLE and reachable by AMF in 3GPP access, the AMFmay start a paging procedure by sending a paging message and invoke anetwork triggered service request procedure. Upon reception of pagingrequest, the UE may initiate the UE triggered service request procedure.

In an example embodiment, if the UE is in CM-CONNECTED over 3GPP accessor non-3GPP access, the AMF may transfer the UE policy container (UEaccess selection and PDU session selection related policy information)received from the PCF to the UE. The UE policy container may comprisethe URSP.

In an example, the UE may update the UE policy provided by the PCF andmay send the result to the AMF. If the AMF received the UE policycontainer and the PCF subscribed to be notified of the reception of theUE policy container, the AMF may send/forward the response of the UE tothe PCF by employing a Namf_NlMessageNotify operation. The PCF maymaintain the latest list of PSIs delivered to the UE and may update thelatest list of PSIs in the UDR/UDM by invoking Nudr_DM_Update (SUPI,policy data, policy set entry, updated PSI data, and/or the like)service operation.

In an example embodiment as depicted in FIG. 25, a registrationprocedure (e.g., the initial registration procedure as depicted in FIG.8 and FIG. 9) may be performed by the UE (e.g., a wireless device, adevice that supports bridge functionality, IEEE 802.1Q, VLAN port,physical bridge port, virtual bridge port, ethernet switch, learningethernet switch, and/or the like).

In an example, the UE may send to a RAN node (e.g., a base station, eNB,gNB, and/or the like) a registration request message e.g., an ANmessage. The registration request message may comprise a TSN supportcapability parameter/flag (e.g., TSN bridge capability supportparameter, TSN bridge capability, and/or the like), AN parameters,registration request (e.g., registration type, SUCI or 5G-GUTI or PEI,last visited TAI (if available), security parameters, requested NSSAI,[mapping of requested NSSAI], default configured NSSAI indication, UEradio capability update, UE MM core network capability, PDU Sessionstatus, List Of PDU sessions to be activated, follow-on request, MICOmode preference, requested DRX parameters, [LADN DNN(s) or indicator ofrequesting LADN information]), UE policy container (the list of PSIs,indication of UE support for ANDSP and the operating system identifier),and/or the like), and/or the like. In an example, the registrationrequest may further comprise the TSN support capability parameter/flag.

In an example, if a 5G-S-TMSI or GUAMI is not included or the 5G-S-TMSIor GUAMI does not indicate a valid AMF, the (R)AN node, based on (R)ATand requested NSSAI, if available may selects an AMF. In an example, theRAN node may select the AMF based on the TSN support capabilityparameter/flag. In an example, the (R)AN may forward the registrationrequest message to the AMF based on the N2 connection of the UE. In anexample, if the (R)AN cannot select an appropriate AMF, it may forwardthe registration request to an AMF which has been configured, in (R)AN,to perform AMF selection.

In an example, the (R)AN may send to the (new) AMF an N2 message. The N2message may be a registration request message. The N2 message maycomprise N2 parameters, the registration request, UE Policy Container,and/or the like. The N2 message may further comprise the TSN supportcapability parameter/flag. When NG-RAN is employed, the N2 parametersmay comprise the selected PLMN ID, location information and cellidentity related to the cell in which the UE is camping, UE contextrequest which may indicate that a UE context including securityinformation requires to be setup at the NG-RAN. When NG-RAN is employed,the N2 parameters may further comprise the establishment cause. In anexample, when the establishment cause is associated with priorityservices (e.g. MPS, MCS, TSN and/or the like), the AMF may include amessage priority header to indicate priority information. Other NFs mayrelay the priority information by including the message priority headerin service-based interfaces.

In an example, the (new) AMF, based on the identifiers of the UE (e.g.,SUPI, and/or the like), may select a UDM. The UDM may select a UDRinstance. If the AMF has changed since the last registration procedure,or if the UE provides a SUPI which doesn't refer to a valid context inthe AMF, or if the UE registers to the same AMF it has alreadyregistered to a non-3GPP access (i.e. the UE is registered over anon-3GPP access and initiates this Registration procedure to add a 3GPPaccess), the (new) AMF may register with the UDM usingNudm_UECM_Registration for the access to be registered (and maysubscribe to be notified when the UDM deregisters this AMF). The AMF mayprovide the indication for homogenous support of IMS voice over PSsessions to the UDM. If the AMF does not have subscription data for theUE, the AMF may retrieve the access and mobility subscription data, SMFselection subscription data and UE context in SMF data by employingNudm_SDM_Get operation, and/or the like. The UDM may retrieve thisinformation from UDR by Nudr_DM_Query, and/or the like. After asuccessful response is received, the AMF may subscribe to be notifiedusing Nudm_SDM_Subscribe when the data requested is modified. The UDMmay subscribe to UDR by Nudr_DM_Subscribe. The GPSI may be provided tothe AMF in the access and mobility subscription data from the UDM if theGPSI is available in the UE subscription data. The UDM may provideindication that the subscription data for network slicing is updated forthe UE. If the UE is subscribed to TSN in the serving PLMN, TSN prioritymay be included in the access and mobility subscription data provided tothe AMF. In an example, the TSN priority may indicate that the user/UEis subscribed to TSN services/system. The TSN priority may be employedin the registration accept message to the UE to inform the UE whetherconfiguration of an access identity is valid within the selected PLMN,network, NPN, and/or the like. In an example, the TSN priority may bepart of system enablers for priority mechanisms. The 3GPP system, 5GSand the 3GPP, 5G QoS model may allow classification and differentiationof services such as TSN, public warning system, SMS over NAS, IMSsupport, emergency services, mission critical service, multimediapriority services, and/or the like, based on subscription-related andinvocation-related priority mechanisms. These mechanisms provideabilities such as invoking, modifying, maintaining, releasing, and/orthe like of service, stream, and/or QoS flows with priority, anddelivering QoS flow packets according to the QoS characteristics undernetwork congestion conditions. Subscription-related priority mechanismsmay comprise the ability to prioritize flows based on subscriptioninformation, including the prioritization of RRC connectionestablishment based on unified access control mechanisms and theestablishment of prioritized QoS Flows. Invocation-related prioritymechanisms may be the ability for the service layer to request/invokethe activation of prioritized QoS flows through an interaction overRx/N5 and packet detection in the UPF. QoS mechanisms applied toestablished QoS flows may include the ability to fulfil the QoScharacteristics of QoS flows through preservation of differentiatedtreatment for prioritized QoS flow and resource distributionprioritization.

The (new) AMF may provide the access type it serves for the UE to theUDM and the access type may be set to 3GPP access. The UDM may store theassociated access type together with the serving AMF and may retain theAMF identity associated to the other access type if any. The UDM maystore in UDR information provided at the AMF registration byNudr_DM_Update, and/or the like. The (new) AMF may create a UE contextfor the UE after getting the access and mobility subscription data fromthe UDM. the access and mobility subscription data may include whetherthe UE is allowed to include NSSAI in the 3GPP access RRC connectionestablishment.

In an example, the AMF may determine/decide to initiate PCFcommunication. If the AMF determines to contact the (V-)PCF identifiedby PCF ID included in UE context from the (old) AMF, the AMF may contactthe (V-)PCF identified by the (V-)PCF ID. If the AMF determines/decidesto perform PCF discovery and selection and the AMF selects a (V)-PCF andmay select an H-PCF (for roaming scenario). In an example, the (new) AMFmay perform an AM policy association modification as depicted in FIG.26. If the (new) AMF contacts the PCF identified by the (V-)PCF IDreceived during inter-AMF mobility, the new AMF may include the PCFID(s) in the Npcf AMPolicyControl Create operation. If the AMF notifiesthe mobility restrictions (e.g. UE location) to the PCF for adjustment,or if the PCF updates the mobility restrictions itself due to someconditions (e.g. application in use, time and date, and/or the like),the PCF may provide the updated mobility restrictions to the AMF. If thesubscription information includes tracing requirements, the AMF mayprovide the PCF with tracing requirements.

In an example, the AMF may send to the SMF aNsmf_PDUSession_UpdateSMContext message/operation, and/or the like. TheAMF may invoke the Nsmf PDUSession_UpdateSMContext operation. TheNsmf_PDUSession_UpdateSMContext operation may be employed to update theAMF-SMF association to support a PDU session and/or to provide SMF withN1/N2 SM information received from the UE or from the AN. The NsmfPDUSession_UpdateSMContext operation message may comprise the TSNcapability support parameter/flag, PDU session ID, N1 SM containerreceived from the UE, N2 SM information received from the AN (e.g. N3addressing information, notification indicating that the QoS targetscannot be fulfilled for a QFI, Secondary RAT Usage Data), operation type(e.g. UP activate, UP deactivate, UP To Be Switched), Serving GWAddress(es) and Serving GW DL TEID(s) for data forwarding during HO from5GS to EPS, UE location information, AN type, UE Time Zone, H-SMFidentifier/address, EBI(s) to be revoked, PDU Session(s) to bere-activated, Direct Forwarding Flag, ARP list, S-NSSAI, Data ForwardingTunnel (setup/release), UE presence in LADN service area, Target ID,Target AMF ID, GUAMI, backup AMF(s) (if NF Type is AMF), indication ofaccess type can be changed, and/or the like.

In an example, the AMF may invoke the Nsmf_PDUSession_ReleaseSMContextservice operation towards the SMF when any PDU session status indicatesthat it is released at the UE, the AMF invokes theNsmf_PDUSession_ReleaseSMContext service operation towards the SMF inorder to release any network resources related to the PDU Session.

In an example, the (new) AMF may send to N3IWF an N2 AMF mobilityrequest ( ) message/command If the AMF has changed and the old AMF hasindicated an existing NGAP UE association towards a N3IWF, the new AMFmay create an NGAP UE association towards the N3IWF to which the UE isconnected. This may release the existing NGAP UE association between theold AMF and the N3IWF. The N3IWF may send to the new AMF an N2 AMFMobility Response 0 message/command

In an example, the new AMF may send to the UE a registration acceptmessage. The registration accept message may comprise 5G-GUTI,registration area, mobility restrictions, PDU session status, allowedNSSAI, [mapping of allowed NSSAI], [configured NSSAI for the servingPLMN], [mapping of configured NSSAI], [rejected S-NSSAIs], periodicregistration update timer, LADN information and accepted MICO mode, IMSVoice over PS session supported Indication, emergency service supportindicator, accepted DRX parameters, network support of Interworkingwithout N26, access stratum connection establishment NSSAI inclusionmode, network slicing subscription change indication, operator-definedaccess category definitions). The allowed NSSAI for the access type forthe UE is included in the N2 message carrying the registration acceptmessage. The AMF may send a registration accept message to the UEindicating that the registration request has been accepted. 5G-GUTI maybe included if the AMF allocates a new 5G-GUTI. If the UE is already inRM-REGISTERED state via another access in the same PLMN, the UE mayemploy the 5G-GUTI received in the registration accept for bothregistrations. If no 5G-GUTI is included in the Registration Accept,then the UE may employ the 5G-GUTI assigned for the existingregistration for the new registration. If the AMF allocates a newregistration area, it may send the registration area to the UE viaregistration accept message. If there is no registration area includedin the registration accept message, the UE may consider the oldregistration area as valid. Mobility restrictions may be included incase mobility restrictions applies for the UE and registration type isnot emergency registration. The AMF may indicate the established PDUsessions to the UE in the PDU session status. The UE may remove locallyany internal resources related to PDU sessions that are not marked asestablished in the received PDU session status. If the AMF invokes theNsmf PDUSession_UpdateSMContext procedure for UP activation of PDUsession(s) and receives rejection from the SMF, then the AMF mayindicate to the UE the PDU session ID and the cause why the user planeresources were not activated. When the UE is connected to the two AMFsbelonging to different PLMN via 3GPP access and non-3GPP access then theUE may remove locally any internal resources related to the PDU sessionof the current PLMN that are not marked as established in received PDUsession status. If the PDU session status information was in theregistration request, the AMF may indicate the PDU session status to theUE. The mapping of allowed NSSAI may be the mapping of one or moreS-NSSAI of the Allowed NSSAI to the HPLMN S-NSSAIs. The mapping ofconfigured NSSAI may be the mapping of one or more S-NSSAI of theconfigured NSSAI for the serving PLMN to the HPLMN S-NSSAIs. The AMF mayinclude in the registration accept message the LADN Information for thelist of LADNs that are available within the registration area determinedby the AMF for the UE. If the UE included MICO mode in the request, thenthe AMF may respond whether MICO mode may be used. The AMF may includeoperator-defined access category definitions to let the UE determine theapplicable operator-specific access category.

In an example, the (new) AMF may send to the UE a registration acceptmessage. The registration accept message may comprise configurations forthe TSN system (e.g., S-NSSAI(s) for the TSN, DNN of the TSN system,and/or the like), 5G-GUTI, registration area, mobility restrictions, PDUsession status, allowed NSSAI, [mapping of allowed NSSAI], [configuredNSSAI for the serving PLMN, NPN, TSN system], [mapping of configuredNSSAI for the TSN system], [rejected S-NSSAIs], periodic registrationupdate timer applicable to the TSN system, LADN information of the TSNsystem, accepted MICO mode for the UE that is part of the TSN bridge,IMS Voice over PS session supported Indication, emergency servicesupport indicator, accepted DRX parameters for the TSN system, networksupport of interworking without N26, access stratum connectionestablishment NSSAI inclusion mode, network slicing subscription changeindication, operator-defined access category definitions, and/or thelike.

In an example, in order to set the TSN support capability parameterindication the AMF may determine to perform a UE capability matchrequest procedure to check the compatibility of the UE and NG-RAN radiocapabilities related to TSN capabilities, TSN system, and/or the like.If the AMF hasn't received TSN system support match indicator from theNG-RAN on time then, based on implementation, the AMF may set TSNcapability support parameter indication and update it at a later stage.

In an example, the new AMF may perform a UE policy associationestablishment procedure as depicted in FIG. 26. The new AMF may send aNpcf UEPolicyControl Create request message to the PCF. The PCF may senda Npcf_UEPolicyControl Create Response to the (new) AMF. In an example,the PCF may trigger/invoke the UE configuration update procedure asdepicted in FIG. 24.

In an example, the UE may send a registration complete message to theAMF when it has successfully updated itself after receiving any of theURSP, [configured NSSAI for the serving PLMN], [mapping of configuredNSSAI] and a network slicing subscription change indication, and/or thelike. The UE may send the registration complete message to the AMF toacknowledge if a new 5G-GUTI was assigned.

In an example, the UE policy association establishment procedure asdepicted in FIG. 26, may comprise the following procedure. In anexample, The AMF may receive the UE policy container from the UE. In anexample, in response to receiving the UE Policy container received fromUE, the AMF may determine/decide to establish UE policy association withthe PCF. The AMF may send a Npcf_UEPolicyControl create request. TheNpcf_UEPolicyControl create request may comprise the TSN supportcapability parameter/flag, SUPI, access type and RAT, PEI, ULI, UE timezone, serving network and UE policy container (the list of stored PSIs,operating system identifier, indication of UE support for ANDSP, and/orthe like). In roaming scenario, based on operator policies, the AMF mayprovide to the V-PCF the PCF ID of the selected H-PCF. The V-PCF maycontact the H-PCF. The PCF may send a Npcf_UEPolicyControl CreateResponse to the AMF. In an example, the PCF may provides the policycontrol request trigger parameters in the Npcf UEPolicyControlUpdateNotify Request to the AMF. The AMF may send a response to the PCF.The PCF may invoke/trigger the UE configuration update procedure, UCU(as depicted in example FIG. 24) to send the URSP, UE access selectionand PDU session selection related policy information, and/or the like tothe UE.

In an example embodiment as depicted in FIG. 27, the UE may send to theRAN node a registration request message. The registration requestmessage may comprise AN parameters, registration request (e.g.,registration type, SUCI or 5G-GUTI or PEI, last visited TAI (ifavailable), security parameters, requested NSSAI, [mapping of requestedNSSAI], default configured NSSAI indication, UE radio capability update,UE MM core network capability, PDU Session status, List Of PDU sessionsto be activated, follow-on request, MICO mode preference, requested DRXparameters, [LADN DNN(s) or indicator of requesting LADN information]),UE policy container (the list of PSIs, indication of UE support forANDSP and the operating system identifier), and/or the like), and/or thelike.

In an example, the (R)AN may send to the (new) AMF an N2 message. The N2message may be a registration request message. The N2 message maycomprise N2 parameters, the registration request, UE Policy Container,and/or the like. When NG-RAN is employed, the N2 parameters may comprisethe selected PLMN ID, location information and cell identity related tothe cell in which the UE is camping, UE context request which mayindicate that a UE context including security information requires to besetup at the NG-RAN. When NG-RAN is employed, the N2 parameters mayfurther comprise the establishment cause. In an example, when theestablishment cause may be associated with priority services (e.g. MPS,MCS, TSN and/or the like), the AMF may include a message priority headerto indicate priority information. Other NFs may relay the priorityinformation by including the message priority header in service-basedinterfaces.

In an example, the AMF may retrieve UE capabilities, the access andmobility subscription data, SMF selection subscription data and UEcontext in SMF data by employing Nudm_SDM_Get operation, and/or thelike. The UDM may retrieve this information from UDR by Nudr_DM_Query,and/or the like. In an example, the UDM, UDR, and/or the like maydetermine that the UE supports TSN bridge functionality. The UDM/UDR maysend a response message to the AMF with an indication that the UEsupports TSN bridge functionality, and/or the like. After a successfulresponse is received, the AMF may subscribe to be notified usingNudm_SDM_Subscribe when the data requested is modified. The UDM maysubscribe to UDR by Nudr_DM_Subscribe. The GPSI may be provided to theAMF in the access and mobility subscription data from the UDM if theGPSI is available in the UE subscription data. The UDM/UDR may provideindication that the UE capabilities, subscription data for networkslicing is updated for the UE. If the UE is subscribed to TSN in theserving PLMN, TSN priority may be included in the access and mobilitysubscription data provided to the AMF. The (new) AMF may provide theaccess type it serves for the UE to the UDM and the access type may beset to 3GPP access. The UDM may store the associated access typetogether with the serving AMF and may retain the AMF identity associatedto the other access type if any. The UDM may store in UDR informationprovided at the AMF registration by Nudr_DM_Update, and/or the like. The(new) AMF may create a UE context for the UE after getting the accessand mobility subscription data from the UDM. the access and mobilitysubscription data may include whether the UE is allowed to include NSSAIin the 3GPP access RRC connection establishment.

In an example, when the AMF receives from the UDM/UDR that the UEsupports TSN bridge functionality, the AMF may interact with the PCF forpolicy association establishment, policy association modification,and/or the like.

As depicted in example FIG. 28 and FIG. 29, when the UE receives theURSP, the UE may employ the URSP to determine parameters for a selectionand/or establishment of a PDU session. If the UE has one or more PDUsession established, the UE may select the proper PDU session to servethe TSN request. The selection may be based on the TSN configurationparameters (received from the network, e.g., via the URSP, registrationaccept message, configuration update message, PCO, and/or the like). Inan example, a first station (e.g., a TSN end station, end station 1,and/or the like) may send a request to the UE via a TSNadaptor/translator, and/or the like. The end station request may be atalker advertisement, a message from a bridge, a stream reservationprotocol (SRP) message, an MSRP message, an IEEE 802.1Q message, abridge PDU (BPDU) message, a spanning tree protocol message, an ethernetframe for a VLAN, and/or the like. The UE may determine that the requestfrom the first station, may require a TSN connection capability. The UEmay employ the URSP to determine a rule that is associated with atraffic descriptor connection capabilities. The traffic descriptorconnection capabilities may be TSN, VLAN bridge, and/or the like. In anexample, the UE may employ the URSP to determine a rule that isassociated with a traffic descriptor indicating a TSN bridge identifier,TSN (virtual/physical) port identifier, TSN (virtual/physical) portpriority, and/or the like. In an example, the UE may employ the URSP todetermine a rule that is associated with an interface e.g., ingressinterface, ingress port, a system identifier, a private networkidentifier (e.g., non-public network NPN), and/or the like, indicatinge.g., a TSN bridge identifier, TSN (virtual/physical) port identifier,TSN (virtual/physical) port priority, a TSN system identifier, and/orthe like. The URSP rule may comprise one or more rules. The one or morerules may comprise a rule precedence, traffic descriptor, and a list ofroute selection descriptors. The traffic descriptor may compriseapplication descriptors/identifiers, IP traffic descriptors, Non-IPtraffic descriptors, DNN, connection capabilities, and/or the like. TheURSP rule associated with the traffic descriptor may comprise a SSC modeselection, slice selection (S-NSSAI(s), network slice ID(s), and/or thelike), PDU session type, non-seamless offload indication, access typepreference, RAT type preference, and/or the like.

In an example as depicted in FIG. 29, the UE may receive a request froma TSN station. Based on the request from the TSN station, the UE mayestablish a PDU session based on the TSN configuration parametersreceived from the network, e.g., via the URSP, registration acceptmessage, configuration update message, PCO, and/or the like.

In an example embodiment as depicted in FIG. 31, the UE mayperform/invoke/initiate the PDU session establishment procedure (FIG. 12and FIG. 13).

In an example, during the PDU session establishment procedure, the UEmay send to the AMF, a NAS message. The NAS message may compriseS-NSSAI(s), DNN, PDU Session ID, Request type, Old PDU Session ID, N1 SMcontainer (PDU Session Establishment Request), and/or the like. The NASmessage may further comprise the TSN support capability parameter/flagindicating that the PDU session may be for the TSN system, for a TSNstation, a TSN bridge (behind the UE), and/or the like. In order toestablish a new PDU session, the UE may generate a new PDU session ID.The UE may initiates the UE requested PDU session establishmentprocedure by the transmission of a NAS message comprising a PDU Sessionestablishment request within the N1 SM container. The PDU sessionestablishment request may comprise a PDU session ID, Requested PDUSession Type, a Requested SSC mode, SGSM Capability PCO, SM PDU DNRequest Container, number of packet filters, and optionally Always-onPDU session requested. The PDU session establishment request may furthercomprise the TSN support capability parameter/flag, and/or the like. TheS-NSSAI description may indicate that a slice for TSN system may berequired. The PDU session type may indicate that the PDU session is fora TSN system, that may support IEEE 802.1Q procedures, and/or the like.

The AMF may determine that the message corresponds to a request for anew PDU session based on that request type indicates initial request andthat the PDU Session ID is not used for any existing PDU Session(s) ofthe UE. If the NAS message does not contain an S-NSSAI, the AMF maydetermine a default S-NSSAI for the requested PDU session according tothe UE subscription, the TSN support capability parameter, and/or thelike. When the NAS message comprises an S-NSSAI but it does not containa DNN, the AMF may determine the DNN for the requested PDU session byselecting the default DNN for this S-NSSAI if the default DNN is presentin the UE's Subscription Information. The serving AMF may select alocally configured DNN for this S-NSSAI. In an example, the AMF mayselect the DNN based on the TSN support capability parameter/flag,and/or the like.

In an example, the AMF may select an SMF. The AMF may select the SMFbased on the TSN support capability parameter/flag. In an example, ifthe PDU session establishment request comprises a network identifier,NPN ID (that supports TSN), and/or the like, the AMF may select the SMFbased on the network ID, NPN ID.

In an example, the AMF may send to the SMF aNsmf_PDUSession_CreateSMContext Request message comprising SUPI, DNN,S-NSSAI(s), PDU Session ID, AMF ID, Request Type, PCF ID, PriorityAccess, N1 SM container (PDU Session Establishment Request, Userlocation information, Access Type, PEI, GPSI, UE presence in LADNservice area, Subscription For PDU Session Status Notification, DNNSelection Mode, Trace Requirements), and/or the like. In an example, theAMF may send to the SMF a Nsmf_PDUSession_UpdateSMContext Requestcomprising SUPI, DNN, S-NSSAI(s), PDU Session ID, AMF ID, Request Type,N1 SM container (PDU Session Establishment Request), User locationinformation, Access Type, RAT type, PEI, and/or the like. TheNsmf_PDUSession_CreateSMContext Request message and/or theNsmf_PDUSession_UpdateSMContext Request message may further comprise theTSN support capability parameter/flag.

In an example, if session management subscription data for correspondingSUPI, DNN and S-NSSAI is not available, the SMF may employ the UDMand/or the UDR to retrieve the session management subscription datausing Nudm_SDM_Get (SUPI, Session Management Subscription data, DNN,S-NSSAI) and may subscribe to be notified when this subscription data ismodified using Nudm_SDM_Subscribe (SUPI, Session Management Subscriptiondata, DNN, S-NSSAI). UDM may get this information from UDR byNudr_DM_Query (SUPI, Subscription Data, Session Management Subscriptiondata, DNN, S-NSSAI) and may subscribe to notifications from UDR for thesame data by Nudr_DM_subscribe. The S-NSSAI used with the UDM maybe theS-NSSAI with value for the HPLMN, or the non-public network. The SMF mayemploy DNN selection mode when deciding whether to retrieve the sessionmanagement subscription data e.g. in case the (DNN, S-NSSAI) is notexplicitly subscribed, the SMF may use local configuration.

In an example, when the SMF does not receive the TSN support capabilityindicator/parameter/flag, the SMF may query UDM/UDR to determine thatthe UE supports TSN bridge capabilities.

In an example, the SMF may send to the AMF aNsmf_PDUSession_CreateSMContext

Response comprising a cause, SM context ID or N1 SM container (PDUSession Reject (Cause)), and/or the like, or anNsmf_PDUSession_UpdateSMContext Response message.

In an example, the SMF may select the PCF. The SMF may perform a SMpolicy association establishment procedure. In an example, the SMF mayperform an SMF initiated SM policy association modification procedure.The SM policy association establishment/modification procedure may beemployed to establish/modify an SM policy association with the PCF andget the default PCC Rules for the PDU session. The GPSI may be includedif available at SMF. If the Request Type in step 3 indicates existingPDU session, the SMF may provide information on the policy controlrequest trigger condition(s) that have been met by an SMF initiated SMpolicy association modification procedure. The PCF may provide policyinformation to the SMF. In an example, the

In an example, during the SM policy associationestablishment/modification procedure, the SMF may determine that the PCCauthorization is required and may request to establish an SM policyassociation with the PCF by invoking Npcf_SMPolicyControl_Createoperation, Npcf_SMPolicyControl_Update request operation and/or thelike. The SMF may include the following information: the TSN supportcapability parameter/flag, SUPI, PDU Session id, PDU Session Type,S-NSSAI, NSI ID (if available), DNN, GPSI (if available), access type,AMF instance identifier and if available, the IPv4 address and/or IPv6network prefix, PEI, User Location Information, UE Time Zone, ServingNetwork, RAT type, charging characteristics, session AMBR, default QoSinformation, trace requirements, internal group identifier, and/or thelike. The SMF may provide trace requirements to the PCF when it hasreceived trace requirements and it has selected a different PCF than theone received from the AMF. If the PCF does not have the subscriber'ssubscription related information, it may send a request to the UDR byinvoking Nudr_DM_Query (SUPI, DNN, S-NSSAI, policy data, PDU sessionpolicy control data, accumulated usage data) service in order to receivethe information related to the PDU Session. The PCF may requestnotifications from the UDR on changes in the subscription information byinvoking Nudr_DM_Subscribe (Policy Data, SUPI, DNN, S-NSSAI,Notification Target Address (Notification Correlation Id), EventReporting Information (continuous reporting), PDU Session policy controldata, Accumulated Usage data) service. In an example, the UDR mayindicate to the PCF that the UE supports TSN capability, TSN bridgecapability, IEEE 802.1Q, and/or the like. The PCF may make theauthorization and the policy decision. The PCF may respond to the SMFwith a Npcf_SMPolicyControl_Create/update response message, and/or thelike. The response may comprise policy information. The policyinformation may be the URSP. The SMF may send the URSP to the UE via theAMF. The SMF may enforce/apply the decision. The SMF may subscribe tothe PCF to changes in the policy decisions. In an example, when the PCFdetermines that the UE supports TSN capacities, the PCF may invoke theUE configuration update procedure and deliver the URSP to the UE via theAMF.

In an example, when the UE indicates to the network that it supports TSNbridge functionality, the network may initiate a configuration update onthe UE. The configuration update may comprise change of network slice(s)e.g., S-NSSAI(s), updating the allowed S-NSSAI(s) of the UE, change ofDNN, and/or the like. The configuration update may comprise a networktriggered session, PDU session modification, service request procedure,and/or the like. The configurations may be updated via a protocolconfiguration update (PCO). The PCO may be included in PDU sessionmodification messages. In an example, the PCO may be a sessionmanagement information element, and/or the like.

In an example, the PCO may employed to transfer external networkprotocol options associated with a PDU session context, a PDP contextactivation, and/or the like. The PCO may employed to transfer additional(protocol) data (e.g. configuration parameters, error codes ormessages/events, and/or the like) associated with an external protocolor an application.

The UE may send a PCO to the AMF requesting TSN configurationinformation. The AMF may send the request to the SMF. The SMF may send arequest to the PCF to determine the TSN system configuration parameterse.g., S-NSSAI, DNN, and/or the like. The AMF may send a request to thePCF to determine the TSN system configuration parameters e.g., S-NSSAI,DNN, and/or the like. The AMF may send the PCO to the UE. The PCO may bepart of a session management procedure, e.g., SM-NAS, NAS, NAS-SM,and/or the like. The session management procedure may comprise a PDUsession modification request, and/or the like that may be send by theSMF to the UE via the AMF. The PCO that is received by the UE maycomprise configuration options for the TSN system, e.g., a list of oneor more S-NSSAIs, one or more DNN(s), PDU session type, access type, RATtype, and/or the like.

In an example, in response to sending the TSN support indication by theUE, the network may trigger change of network slice (S-NSSAI(s)), changeof DNN, and/or the like for the UE. The UE may invoke a PDU sessionmodification procedure, a session management procedure, and/or the like.The network initiated PDU session modification may be performed when thePCF performs a PCF initiated SM policy association modificationprocedure to notify SMF about the modification of policies. This mayhave been triggered by a policy decision or upon TSN AF requests, e.g.application function influence on traffic routing, and/or the like. Inan example, the SMF initiated request for modification may be performedwhen the UDM updates the subscription data of SMF byNudm_SDM_Notification (SUPI, session management subscription data). TheSMF may update the session management subscription data and mayacknowledge the UDM by returning an Acknowledgment message comprisingthe SUPI, and/or the like.

In an example, for the SMF requested PDU session modification, the SMFmay invokes Namf_Communication_N1N2MessageTransfer (e.g., comprising N2SM information (PDU Session ID, QFI(s), QoS Profile(s), Session-AMBR),N1 SM container (PDU session modification command (PDU Session ID, QoSrule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s)associated with the QoS rule(s), QoS rule operation and QoS Flow levelQoS parameters operation, Session-AMBR)), and/or the like). If the UE isin CM-IDLE state and an ATC is activated, the AMF may update and storethe UE context based on the Namf_Communication_N1N2MessageTransfer. Whenthe UE is reachable e.g., when the UE enters CM-CONNECTED state, the AMFforwards the N1 message to synchronize the UE context with the UE. TheAMF may send N2 PDU session request (N2 SM information received fromSMF, NAS message (PDU Session ID, N1 SM container (PDU sessionmodification command))) message to the (R)AN. The (R)AN may issue ANspecific signaling exchange with the UE that is related with theinformation received from SMF. For example, in case of a NG-RAN, an RRCconnection reconfiguration may take place with the UE modifying the(R)AN resources related to the PDU Session. In an example, the PDUsession modification command may comprise an indication to changenetwork slice(s), S-NSSAI(s), DNN, and/or the like. The S-NSSAI(s), DNN,and/or the like may be associated to the TSN system, TSN bridgefunction, and/or the like.

As depicted in an example FIG. 30, the wireless device may have one ormore PDU sessions established. The one or more PDU sessions may be forthe TSN system e.g., configured for the TSN system. In an example, aCNC/CUC may request the TSN AF for a profile generation or update. Theprofile generation/update may comprise modification of 3GPP systemconfigurations, QoS update, resource allocation/reservation, and/or thelike. The TSN AF may interact with the PCF via an NEF. The TSN AF mayrequest the PCF to generate a TSN configuration, a TSN QoS profile,and/or the like. The PCF may accept the request. The PCF may send arequest to the SMF for delivery of the updated policy, the TSN systemconfiguration for the 3GPP system, URSP, and/or the like. The SMF maysend a message to the AMF to request transfer of policies andconfigurations to the UE (the wireless device).

In an example, the PCF may send a policy delivery request message,and/or the like to the AMF to request delivery of the policies andconfigurations to the UE. The SMF may update the configuration of theUPF by employing N4 session level or node level procedures.

In an example, when the SMF receives the policies and configurationsfrom the PCF, the SMF may invoke/initiate a PDU session modificationprocedure. The SMF may employ a invokesNamf_Communication_N1N2MessageTransfer message, and/or the like. TheNamf_Communication_N1N2MessageTransfer message may comprise a PCO IE.The PCO may comprise the TSN configuration information.

In an example, FIG. 41 depicts example rules in a URSP. In an example, aURSP rule may apply to a traffic descriptor application identifier andconnection capabilities indicating TSN. The rule may indicate that uponestablishment or modification of a PDU session that may be employed forthe TSN system, S-NSSAI-a, DNN_1 and access type non-3GPP may beincluded in the establishment/modification request. In an example, arule may be applied to any application identifier, and for connectioncapabilities=TSN. The rule may indicate that uponestablishment/modification/configuration of a PDU session or acommunication network system serving the TSN system, S-NSSAI-b may beselected for slice, access type of 3GPP may be employed, and/or thelike.

In an example embodiment, a wireless device (a UE, an ethernetbridge/switch device, and/or the like) may send to an access andmobility management function, a registration request message. Theregistration request message may comprise a TSN bridge capabilitysupport parameter that may indicate that the wireless device may supporta TSN bridge functionality. In an example, the wireless device, mayreceive from a policy control function via the access and mobilitymanagement function based on the TSN bridge capability supportparameter, a configuration update message. The configuration updatemessage may comprise at least one route configuration rule. The wirelessdevice may determine based on the TSN request message and the at leastone route configuration rule, one or more configuration parameters forestablishing a packet data unit (PDU) session. The wireless device maysend to the access and mobility management function, a request toestablish the PDU session. The request may comprise the one or moreconfiguration parameters, and/or the like.

In an example embodiment, the TSN bridge capability support parametermay comprise number of ports on the wireless device, a parameterindicating that the wireless device supports spanning tree protocol, aparameter indicating that the wireless device supports TSN bridgefunctions, and/or the like.

In an example embodiment, the wireless device may receive from a firststation (e.g., a TSN bridge, VLAN switch, a TSN end station, and/or thelike), a TSN request message. The TSN request message may requireestablishing a packet data unit (PDU) session for the TSN system.

In an example, the determining by the wireless device may be based onthe TSN request message that requires establishing a packet data unit(PDU) session. In an example, the TSN request may be a streamreservation protocol message. In an example, the TSN request may bereceived from a TSN bridge. In an example, the TSN request may bereceived from a TSN station (TSN end station). In an example, thedetermining of the one or more configuration parameters may be furtherbased on the TSN request message.

In an example, the at least one route configuration rule may be a userequipment route selection policy (URSP). The at least one routeconfiguration rule may comprise a traffic descriptor of the TSN system.The traffic descriptor of the TSN system may comprise an identifier of aTSN bridge, an identifier of a traffic descriptor of the TSN system, apriority value of the traffic descriptor of the TSN system, and/or thelike. The at least one route configuration rule may comprise a TSNconnection capability. In an example, the configuration update messagemay comprise a protocol configuration option (PCO) information element.The configuration update message may be a registration accept message.

In an example, the one or more configuration parameters may comprise atleast one of a single network slice selection assistance information(S-NSSAI) associated with the TSN system, a data network name (DNN)associated with the TSN system, a PDU session type associated with theTSN system, an access type associated with the TSN system, a radioaccess technology (RAT) type associated with the TSN system, and/or thelike.

In an example, the configuration update message may be a registrationaccept message.

In an example, the registration request message may further comprise anidentifier of the wireless device, a subscription concealed identifier(SUCI), one or more security parameters, one or more single networkslice selection assistance information (S-NSSAI), one or morediscontinuous reception (DRX) parameters, and/or the like.

In an example, the wireless device may receive from the AMF aregistration accept message. The registration accept message maycomprise a network slicing subscription change indication, a singlenetwork slice selection assistance information (S-NSSAI) associated withthe TSN system, one or more discontinuous reception (DRX) parameters forthe wireless device that supports the TSN bridge functionality, a localarea data network (LADN) Information for the TSN system, an acceptedMICO mode preference for the TSN system, a data network name (DNN)associated with the TSN system, a PDU session type preference associatedwith the TSN system, an access type associated with the TSN system, aradio access technology (RAT) type associated with the TSN system,and/or the like.

In an example, a base station may select the AMF based on the TSN bridgecapability support parameter. The AMF may select a session managementfunction (SMF) based on the TSN bridge capability support parameter.

In an example embodiment, a wireless device may send to an access andmobility management function, a registration request message comprisinga TSN bridge capability support parameter that indicates that thewireless device may support a TSN bridge functionality. The wirelessdevice may receive from a policy control function via the access andmobility management function based on the TSN bridge capability supportparameter, a configuration update message. The configuration updatemessage may comprise at least one route configuration rule, and/or thelike. The wireless device may determine based on the configurationupdate message and the at least one route configuration rule, one ormore configuration parameters associated with a traffic descriptor forthe TSN system, for modifying a packet data unit (PDU) session. Thewireless device may send to the access and mobility management function,a request to modify the PDU session. The request may comprise the one ormore configuration parameters.

In an example, the TSN bridge capability support parameter may comprisenumber of ports on the wireless device, a parameter indicating that thewireless device supports spanning tree protocol, a parameter indicatingthat the wireless device supports TSN bridge functions, a hardwarecapability of the UE to provide physical/virtual ports that supportVLAN, IEEE 802.1Q, MAC address learning, and/or the like. In an example,the one or more configuration parameters may comprise a user equipmentroute selection policy (URSP). The URSP may comprise the trafficdescriptor of the TSN system. The traffic descriptor for the TSN systemmay comprise one or more of a connection capabilities type indicator, anidentifier of the TSN bridge, an identifier of a port, and/or the like.The connection capabilities type may be TSN connection capabilityindicator (e.g., traffic descriptor □ connection capabilities=TSN,and/or the like).

In an example, the one or more configuration parameters may comprise atleast one of a single network slice selection assistance information(S-NSSAI) for the TSN system, a data network name (DNN) for the TSNsystem, a PDU session type for the TSN system, an access type for theTSN system, a radio access technology (RAT) type for the TSN system,and/or the like.

In an example, the configuration update message may comprise a protocolconfiguration option (PCO) information element. The configuration updatemessage may be a registration accept message. In an example, thedetermining to modify the PDU session may be in response to receivingthe configuration update message. The determining to modify the PDUsession may be in response to receiving a TSN request message. The TSNrequest message may be a stream reservation protocol message. The TSNrequest message may be received from a TSN bridge. The TSN requestmessage may be received from a TSN station (TSN end station).

In an example, the registration request message may further comprise anidentifier of the wireless device, a subscription concealed identifier(SUCI), one or more security parameters, one or more single networkslice selection assistance information (S-NSSAI), one or morediscontinuous reception (DRX) parameters, and/or the like. The wirelessdevice may receive from the AMF a registration accept message. Theregistration accept message may comprise a network slicing subscriptionchange indication, a single network slice selection assistanceinformation (S-NSSAI) associated with the TSN system, one or morediscontinuous reception (DRX) parameters for the wireless device thatsupports the TSN bridge functionality, a local area data network (LADN)Information for the TSN system, an accepted MICO mode preference for theTSN system, a data network name (DNN) associated with the TSN system, aPDU session type preference associated with the TSN system, an accesstype associated with the TSN system, a radio access technology (RAT)type associated with the TSN system, and/or the like.

In an example, a base station may select the AMF based on the TSN bridgecapability support parameter. The AMF may select a session managementfunction (SMF) based on the TSN bridge capability support parameter.

In an example embodiment, an access and mobility management function(AMF) may receive from a wireless device, a registration request messagefor a network that supports time sensitive network (TSN). The AMF maydetermine that the wireless device may support TSN bridge capability.The AMF may send to a policy control function (PCF), a policyassociation request message comprising a TSN bridge capability supportparameter. The AMF may receive from the PCF, a route selection policy.The route selection policy may comprise one or more configurationparameters of the wireless device that may correspond to a trafficdescriptor for a TSN system. The AMF may send to the wireless device,the route selection policy. The AMF may send to the wireless device, aregistration accept message. The AMF may receive from the wirelessdevice, a packet data unit (PDU) session establishment/modificationrequest message. The PDU session establishment/modification requestmessage may comprise the one or more configuration parameters, and/orthe like.

In an example, the AMF may send to a UDM/UDR a query request fordetermining one or more capabilities of the wireless device. The AMF mayreceive from the UDM/UDR, a query response message indicating that thewireless device supports TSN bridge capability.

In an example, the registration request message may further comprise theTSN bridge capability support parameter. The determining may be based onthe registration request message.

In an example embodiment, a policy control function (PCF) may receivefrom an application function of a time sensitive network (TSN) system, arequest to generate a profile for the TSN system. The PCF may determinebased on the request, a route selection policy comprising one or moreconfiguration parameters for the TSN system. The PCF may send to awireless device the route selection policy that corresponds to a trafficdescriptor for the TSN system.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 47 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 4710, a wireless device sends to an accessand mobility management function (AMF), a message comprising a TSNbridge capability support parameter that indicates that the wirelessdevice supports a TSN bridge functionality. At 4720, the wireless devicereceives from the AMF and based on the TSN bridge capability supportparameter, a configuration update message comprising at least one routeconfiguration rule. At 4730, the wireless device sends to the AMF, arequest to establish the PDU session, the request comprising one or moreconfiguration parameters determined based on the at least one routeconfiguration rule.

FIG. 48 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 4810, an AMF receives from a wireless device,a message comprising a time sensitive networking (TSN) bridge capabilitysupport parameter that indicates that the wireless device supports a TSNbridge functionality. At 4820, the AMF determines that the wirelessdevice supports the TSN bridge functionality. At 4830, the AMF sends toa policy control function (PCF), a policy association request messagecomprising a the TSN bridge capability support parameter. At 4840, theAMF receives from the PCF, a route selection policy comprising one ormore configuration parameters of the wireless device that correspond toa traffic descriptor for a TSN system. At 4850, the AMF sends to thewireless device, the configuration update message comprising the atleast one route configuration rule route. At 4860, the AMF sends to thewireless device a registration accept message. At 4870, the AMF receivesfrom the wireless device, a request to establish a protocol data unit(PDU) session, the request comprising one or more configurationparameters determined based on the at least one route configurationrule.

In an example embodiment, the TSN bridge capability support parametermay comprise a number of ports on the wireless device, a parameterindicating that the wireless device supports spanning tree protocol, aparameter indicating that the wireless device supports TSN bridgefunctions. The wireless device may receive from a first station (e.g.,TSN end station), a TSN request message that requires establishing apacket data unit (PDU) session, wherein the determining the one or moreconfiguration parameters may be further based on the TSN requestmessage. The TSN request may be a stream reservation protocol message.The TSN request may be received from a TSN bridge. The at least oneroute configuration rule may be a user equipment route selection policy(URSP). The URSP may comprise a traffic descriptor of the TSN systemcomprising: an identifier of a TSN bridge, an identifier of a trafficdescriptor of the TSN system, a priority value of the traffic descriptorof the TSN system. The URSP may comprise a TSN connection capability.The configuration update message may comprise a protocol configurationoption (PCO) information element. The configuration update message maybe a registration accept message. The one or more configurationparameters may comprise at least one of: a single network sliceselection assistance information (S-NSSAI) associated with the TSNsystem, a data network name (DNN) associated with the TSN system, a PDUsession type associated with the TSN system, an access type associatedwith the TSN system, a radio access technology (RAT) type associatedwith the TSN system, and/or the like.

In an example embodiment, a wireless device may comprise one or moreprocessors, memory storing instructions that, when executed by the oneor more processors, cause the wireless device to send, to an access andmobility management function (AMF), a message comprising a timesensitive networking (TSN) bridge capability support parameter thatindicates that the wireless device supports a TSN bridge functionality,receive, from the AMF and based on the TSN bridge capability supportparameter, a configuration update message comprising at least one routeconfiguration rule, and send, to the AMF, a request to establish the PDUsession. The request may comprise one or more configuration parametersdetermined based on the at least one route configuration rule. The TSNbridge capability support parameter may comprise a number of ports onthe wireless device, a parameter indicating that the wireless devicesupports spanning tree protocol, a parameter indicating that thewireless device supports TSN bridge functions, and/or the like. Theinstructions may further cause the wireless device to receive, from afirst station, a TSN request message that requires establishing a packetdata unit (PDU) session, wherein the determining the one or moreconfiguration parameters is further based on the TSN request message.The TSN request may be a stream reservation protocol message. The TSNrequest may be received from a TSN bridge. The at least one routeconfiguration rule is a user equipment route selection policy (URSP),wherein the URSP may comprise a traffic descriptor of the TSN systemcomprising: an identifier of a TSN bridge, an identifier of a trafficdescriptor of the TSN system, and/or a priority value of the trafficdescriptor of the TSN system. The URSP may comprise a TSN connectioncapability. The configuration update message may comprise a protocolconfiguration option (PCO) information element. The configuration updatemessage may be a registration accept message. The one or moreconfiguration parameters may comprise at least one of: a single networkslice selection assistance information (S-NSSAI) associated with the TSNsystem, a data network name (DNN) associated with the TSN system, a PDUsession type associated with the TSN system, an access type associatedwith the TSN system and/or a radio access technology (RAT) typeassociated with the TSN system.

In an example, a system may comprise a wireless device that may compriseone or more first processors, first memory storing first instructionsthat, when executed by the one or more first processors, cause thewireless device to send a message comprising a time sensitive networking(TSN) bridge capability support parameter that indicates that thewireless device supports a TSN bridge functionality, receive, from theAMF and based on the TSN bridge capability support parameter, aconfiguration update message comprising at least one route configurationrule, and send, to the AMF, a request to establish the PDU session, therequest comprising one or more configuration parameters determined basedon the at least one route configuration rule. The system may comprise anaccess and mobility management function (AMF) comprising: one or moresecond processors, second memory storing second instructions that, whenexecuted by the one or more second processors, cause the AMF to receive,from the wireless device, the message, determine that the wirelessdevice supports the TSN bridge functionality, send, to a policy controlfunction (PCF), a policy association request message comprising the TSNbridge capability support parameter, receive, from the PCF, a routeselection policy comprising one or more configuration parameters of thewireless device that correspond to a traffic descriptor for a TSNsystem, send to the wireless device, the configuration update messagecomprising the at least one route configuration rule, send to thewireless device, a registration accept message, and receive, from thewireless device, the request to establish the PDU session. The at leastone route configuration rule may be a user equipment route selectionpolicy (URSP). The URSP may comprise: a traffic descriptor of the TSNsystem comprising: an identifier of a TSN bridge, an identifier of atraffic descriptor of the TSN system, a priority value of the trafficdescriptor of the TSN system. The URSP may comprise a TSN connectioncapability.

In an example embodiment, an access and mobility management function(AMF) may receive from a wireless device, a registration request messagefor a network that supports time sensitive network (TSN). The AMF maydetermine that wireless device supports TSN bridge capability. The AMFmay send to a policy control function (PCF), a policy associationrequest message comprising a TSN bridge capability support parameter.The AMF may receive from the PCF, a route selection policy comprisingone or more configuration parameters of the wireless device thatcorresponds to a traffic descriptor for a TSN system. The AMF may sendto the wireless device, the route selection policy. The AMF may send tothe wireless device, a registration accept message. The registrationaccept message may comprise the route selection policy. The AMF mayreceive from the wireless device, a packet data unit (PDU) sessionestablishment/modification request comprising the one or moreconfiguration parameters. In an example, the AMF may send to a UDM/UDR aquery request for determining one or more capabilities of the wirelessdevice. The AMF may receive from the UDM/UDR, a query response messageindicating that the wireless device supports TSN bridge capability. Theregistration request message may further comprise the TSN bridgecapability support parameter. The determining may be based on theregistration request message.

In an example embodiment, a policy control function (PCF) may receivefrom an application function of a time sensitive network (TSN) system, arequest to generate a profile for the TSN system. The PCF may determinebased on the request, a route selection policy comprising one or moreconfiguration parameters for the TSN system. The PCF may send to awireless device the route selection policy that corresponds to a trafficdescriptor for the TSN system.

In this specification, a and an and similar phrases are to beinterpreted as at least one and one or more. In this specification, theterm may is to be interpreted as may, for example. In other words, theterm may is indicative that the phrase following the term may is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments. If A and Bare sets and every element of A is also an element of B, A is called asubset of B. In this specification, only non-empty sets and subsets areconsidered. For example, possible subsets of B={cell1, cell2} are:{cell1}, {cell2}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, which may be behaviorally equivalent. For example,modules may be implemented as a software routine written in a computerlanguage configured to be executed by a hardware machine (such as C,C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device.Finally, it needs to be emphasized that the above mentioned technologiesare often employed in combination to achieve the result of a functionalmodule.

Example embodiments of the invention may be implemented using variousphysical and/or virtual network elements, software defined networking,virtual network functions.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using 5G AN. However, one skilled in the art will recognize thatembodiments of the invention may also be implemented in a systemcomprising one or more legacy systems or LTE. The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. A limited number of example combinations are shownto indicate to one skilled in the art the possibility of features thatmay be combined in various embodiments to create enhanced transmissionand reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposes.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or optionally usedin some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language means for or step for be interpreted under 35 U.S.C.112. Claims that do not expressly include the phrase means for or stepfor are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: sending, by a wireless device to an access andmobility management function (AMF), a message comprising a timesensitive networking (TSN) bridge capability support parameter thatindicates that the wireless device supports a TSN bridge functionality;receiving, by the wireless device, from the AMF, and based on the TSNbridge capability support parameter, a configuration update messagecomprising at least one route configuration rule; and sending, by thewireless device to the AMF, a request to establish a protocol data unit(PDU) session, the request comprising one or more configurationparameters determined based on the at least one route configurationrule.
 2. The method of claim 1, wherein the TSN bridge capabilitysupport parameter comprises: a number of ports on the wireless device; aparameter indicating that the wireless device supports spanning treeprotocol; and a parameter indicating that the wireless device supportsTSN bridge functions.
 3. The method of claim 1, further comprisingreceiving, by the wireless device from a first station, a TSN requestmessage that requires establishing a packet data unit (PDU) session,wherein the determining the one or more configuration parameters isfurther based on the TSN request message.
 4. The method of claim 3,wherein the TSN request is a stream reservation protocol message.
 5. Themethod of claim 3, wherein the TSN request is received from a TSNbridge.
 6. The method of claim 1, wherein the at least one routeconfiguration rule is a user equipment route selection policy (URSP),wherein the URSP comprises: a traffic descriptor of the TSN systemcomprising: an identifier of a TSN bridge; an identifier of a trafficdescriptor of the TSN system; and a priority value of the trafficdescriptor of the TSN system; and a TSN connection capability.
 7. Themethod of claim 1, wherein the configuration update message comprises aprotocol configuration option (PCO) information element.
 8. The methodof claim 1, wherein the configuration update message is a registrationaccept message.
 9. The method of claim 1, wherein the one or moreconfiguration parameters comprises at least one of: a single networkslice selection assistance information (S-NSSAI) associated with the TSNsystem; a data network name (DNN) associated with the TSN system; a PDUsession type associated with the TSN system; an access type associatedwith the TSN system; or a radio access technology (RAT) type associatedwith the TSN system.
 10. A wireless device comprising: one or moreprocessors; memory storing instructions that, when executed by the oneor more processors, cause the wireless device to: send, to an access andmobility management function (AMF), a message comprising a timesensitive networking (TSN) bridge capability support parameter thatindicates that the wireless device supports a TSN bridge functionality;receive, from the AMF and based on the TSN bridge capability supportparameter, a configuration update message comprising at least one routeconfiguration rule; and send, to the AMF, a request to establish the PDUsession, the request comprising one or more configuration parametersdetermined based on the at least one route configuration rule.
 11. Thewireless device of claim 10, wherein the TSN bridge capability supportparameter comprises: a number of ports on the wireless device; aparameter indicating that the wireless device supports spanning treeprotocol; and a parameter indicating that the wireless device supportsTSN bridge functions.
 12. The wireless device of claim 10, wherein theinstructions further cause the wireless device to receive, from a firststation, a TSN request message that requires establishing a packet dataunit (PDU) session, wherein the determining the one or moreconfiguration parameters is further based on the TSN request message.13. The wireless device of claim 12, wherein the TSN request is a streamreservation protocol message.
 14. The wireless device of claim 12,wherein the TSN request is received from a TSN bridge.
 15. The wirelessdevice of claim 10, wherein the at least one route configuration rule isa user equipment route selection policy (URSP), wherein the URSPcomprises: a traffic descriptor of the TSN system comprising: anidentifier of a TSN bridge; an identifier of a traffic descriptor of theTSN system; and a priority value of the traffic descriptor of the TSNsystem; and a TSN connection capability.
 16. The wireless device ofclaim 10, wherein the configuration update message comprises a protocolconfiguration option (PCO) information element.
 17. The wireless deviceof claim 10, wherein the configuration update message is a registrationaccept message.
 18. The wireless device of claim 10, wherein the one ormore configuration parameters comprises at least one of: a singlenetwork slice selection assistance information (S-NSSAI) associated withthe TSN system; a data network name (DNN) associated with the TSNsystem; a PDU session type associated with the TSN system; an accesstype associated with the TSN system; or a radio access technology (RAT)type associated with the TSN system.
 19. A system comprising: a wirelessdevice comprising: one or more first processors; first memory storingfirst instructions that, when executed by the one or more firstprocessors, cause the wireless device to: send a message comprising atime sensitive networking (TSN) bridge capability support parameter thatindicates that the wireless device supports a TSN bridge functionality;receive, from the AMF and based on the TSN bridge capability supportparameter, a configuration update message comprising at least one routeconfiguration rule; and send, to the AMF, a request to establish the PDUsession, the request comprising one or more configuration parametersdetermined based on the at least one route configuration rule; and anaccess and mobility management function (AMF) comprising: one or moresecond processors; second memory storing second instructions that, whenexecuted by the one or more second processors, cause the AMF to:receive, from the wireless device, the message; determine that thewireless device supports the TSN bridge functionality; send, to a policycontrol function (PCF), a policy association request message comprisingthe TSN bridge capability support parameter; receive, from the PCF, aroute selection policy comprising one or more configuration parametersof the wireless device that correspond to a traffic descriptor for a TSNsystem; send, to the wireless device, the configuration update messagecomprising the at least one route configuration rule; send, to thewireless device, a registration accept message; and receive, from thewireless device, the request to establish the PDU session.
 20. Thesystem of claim 19, wherein the at least one route configuration rule isa user equipment route selection policy (URSP), wherein the URSPcomprises: a traffic descriptor of the TSN system comprising: anidentifier of a TSN bridge; an identifier of a traffic descriptor of theTSN system; and a priority value of the traffic descriptor of the TSNsystem; and a TSN connection capability.